clean-cache
Installation
SKILL.md
Batch Project Cache Cleanup (Clean Cache)
Description
When developing multiple Flutter/Android/iOS projects, build artifacts and dependency caches grow rapidly. This Skill batch-scans the workspace, performs tiered cleanup by safety level, and frees disk space while preserving global dependency caches to avoid re-downloading on the next build.
Rules
Rule 0 — Safety Tiers (Core Principle)
Cleanup is divided into three tiers. Only L1 is executed by default; L2/L3 require explicit user confirmation:
| Tier | What Gets Deleted | Rebuild Cost | Estimated Space Freed |
|---|---|---|---|
| L1 Safe Cleanup | Build artifacts (build/, DerivedData, .dart_tool/, bazel-*) + stale dev tool caches (Homebrew old version packages, Bazel global cache) | Recompile only, no network cost | Large |
| L2 Dependency Cleanup | Project-level dependencies (Pods/, node_modules/, .gradle/caches/) | Requires pod install / npm install / gradle sync, but recovers from global cache, relatively fast |
Medium |
| L3 Deep Cleanup | Global caches (~/.gradle/caches/, CocoaPods repo index, Pub global cache) | All projects need to re-download on first build, very slow | Small |
Key distinction: L2 deletes project-internal Pods/, node_modules/, but global caches remain (~/.cocoapods/repos/, npm cache, ~/.gradle/caches/), so re-installing will mostly recover packages from local cache without re-downloading.