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 workflows, designed to remove build artifacts and temporary files to ensure a pristine environment. It helps developers resolve compilation inconsistencies, handle dependency changes, and troubleshoot persistent build errors by facilitating a completely fresh rebuild of the project.
Use Cases
- Troubleshooting build failures: Use this skill to resolve 'strange' or unexplained compilation errors that may be caused by stale or corrupted build artifacts.
- Dependency management: Run a clean operation after updating project dependencies or modifying configuration files to ensure the next build is fully synchronized with the new environment.
- Pre-deployment preparation: Execute a clean build before generating production-ready binaries to guarantee that no legacy files or debug artifacts are included in the final package.
- Disk space optimization: Periodically clear out large build directories and temporary object files to reclaim storage space during long-term development projects.
| 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