メニュー
Reclaim disk space by cleaning build artifacts, dependency caches, and benchmark repos. Auto-invokes before merges, releases, and after big branch switches — or whenever the user asks to clean up, free space, or trim the repo.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | cleanup |
| description | Reclaim disk space by cleaning build artifacts, dependency caches, and benchmark repos. Auto-invokes before merges, releases, and after big branch switches — or whenever the user asks to clean up, free space, or trim the repo. |
Reclaim disk space eaten by Rust build artifacts, node_modules, benchmark repos, and other transient files.
Auto-invoke proactively when:
main, release/*)scripts/release.sh (pairs with the release skill)Do NOT auto-invoke when:
| Target | Typical size | Command |
|---|---|---|
| Debug build artifacts | ~16 GB | cargo clean |
| Release build artifacts | ~1.2 GB | (included in cargo clean) |
cargo clean
Note: This wipes all build artifacts (debug + release). The next
cargo buildorcargo testwill recompile from scratch (~2-5 min). Only run this when the user isn't mid-compile.
| Target | Typical size | Command |
|---|---|---|
| Benchmark repos | ~1.1 GB | rm -rf benchmarks/repos/ |
| Benchmark results | ~2.4 MB | rm -rf benchmarks/rust-results/ |
rm -rf benchmarks/repos/ benchmarks/rust-results/
These are cloned/generated on demand by the benchmark runner. Safe to delete anytime.
| Target | Typical size | Command |
|---|---|---|
website/node_modules/ | ~272 MB | rm -rf website/node_modules/ |
website/dist/ | ~6 MB | rm -rf website/dist/ |
website/.next/ | varies | rm -rf website/.next/ |
rm -rf website/node_modules/ website/dist/ website/.next/
Reinstall with
cd website && npm install.
| Target | Typical size | Command |
|---|---|---|
sdks/rust/target/ | ~94 MB | cd sdks/rust && cargo clean |
sdks/typescript/node_modules/ | ~32 MB | rm -rf sdks/typescript/node_modules/ |
| Target | Typical size | Command |
|---|---|---|
.git/ repack | varies | git gc --aggressive --prune=now |
Only if the user explicitly asks. Git history is precious.
Show the current footprint. Run:
du -sh . target/ benchmarks/repos/ website/node_modules/ sdks/
Give the user a quick summary: "Repo is X GB, Y GB is reclaimable."
Pick the right tier. Ask what they want cleaned, or suggest based on context:
Confirm before deleting. Show exactly what will be removed and how much space it'll free. Get a yes/no.
Run the cleanup. Execute the appropriate commands.
Show the after state. Run du -sh . again and report the savings.
| Scenario | Before | After | Saved |
|---|---|---|---|
cargo clean only | 19 GB | ~2 GB | ~17 GB |
| Full clean (all tiers) | 19 GB | ~35 MB | ~19 GB |
| Just benchmarks + website | 19 GB | ~17.6 GB | ~1.4 GB |
.git/ or any git refscargo clean during an active cargo build/test — check with the user firstBuild, test, or debug a statico plugin. Use when the user wants to write a project-specific rule, scaffold a plugin, or investigate plugin behavior.
Keep statico's user-facing documentation in lockstep with code changes. Auto-invoke proactively whenever the user adds, removes, or modifies CLI flags, subcommands, config keys (`.statico.toml` / `StaticoConfig`), output formats, plugin hooks, plugin protocol fields, the public Rust API (`src/lib.rs` re-exports), template content (`templates/`), or framework profiles. Also invoke when bumping `Cargo.toml` `version`, `rust-version`, or dependency versions that change behavior, and when the user mentions "ship", "release", "publish", or "the docs are stale". Verifies README.md, CHANGELOG.md, the files under `docs/`, the templates under `templates/`, and the example plugin under `examples/plugins/`. Default action is to AUDIT and report drift; only edit when the user confirms or the drift is mechanically obvious (e.g., the README CLI table is missing a flag we just merged).
Run a statico code health analysis on the current project. Presents a human-readable summary of dead code, unused exports, circular dependencies, and overall health score. Use when asked to check code health, find dead code, or review code quality.
Interactive dead code cleanup using statico analysis. Identifies dead files, presents them with context, and helps safely remove them one by one. Use when asked to clean up dead code, remove unused files, or reduce codebase size.
Measure the impact of refactoring using statico before/after analysis. Snapshots code health before changes and compares after. Use when planning or completing a refactoring, measuring code quality improvements, or verifying cleanup effectiveness.
Develop, test, and debug statico plugins. Use when creating plugins, modifying plugin code, or running the plugin development workflow (init, build, run, doctor).