clean
Remove build artifacts for a fresh rebuild. Use when the user wants to clean the project, start fresh, or troubleshoot build issues.
When & Why to Use This Skill
The 'clean' skill is an essential utility for software development and project maintenance, designed to automate the removal of build artifacts and temporary files. By clearing the build directory, it ensures a pristine environment for fresh compilations, effectively resolving issues related to stale caches, dependency conflicts, or corrupted build states to streamline the development workflow.
Use Cases
- Troubleshooting persistent build errors: Quickly eliminate 'ghost' bugs and compilation failures caused by outdated or corrupted artifacts in the build directory.
- Dependency management: Ensure a completely fresh build after updating project dependencies or changing environment configurations to prevent version mismatch issues.
- Pre-deployment preparation: Use as a standard cleanup step before running final production builds to guarantee that the executable is compiled from a clean state without legacy interference.
- Disk space optimization: Reclaim storage space by removing large, unnecessary compiled binaries and temporary build files when they are no longer needed.
| name | clean |
|---|---|
| description | Remove build artifacts for a fresh rebuild. Use when the user wants to clean the project, start fresh, or troubleshoot build issues. |
Clean Build Artifacts
Removes the build directory and all compiled artifacts to enable a fresh rebuild.
Instructions
- Run the clean command:
make clean
When to Use
Use this skill when:
- You encounter strange build errors
- Dependencies have changed
- You want to ensure a completely fresh build
- Before running the
buildskill if you suspect stale artifacts
Notes
- This is a destructive operation - all build artifacts will be removed
- You will need to run the
buildskill after cleaning - The source code is never affected, only the build/ directory