rot
SolidFind dead, stale, and deprecated code left behind — rung 4, ALONE. Use when the user says "procoder rot", "find dead code", "what can I delete", "unused exports", "stale code", "deprecated code", "unused dependencies", "what's rotting in here", or invokes /procoder:rot. Reports deletions with reachability evidence; never deletes.
Install
Quality Score: 84/100
Skill Content
Details
- Author
- azrtydxb
- Repository
- azrtydxb/procoder
- Created
- 3 weeks ago
- Last Updated
- today
- Language
- Go
- License
- Apache-2.0
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
audit
Audit a whole repository against procoder's four rungs — SAFE, TRUE, OBVIOUS, ALONE. Use when the user says "procoder audit", "audit this codebase", "audit the whole repo", "audit the entire codebase", "where is this codebase weakest", "how bad is this repo", or invokes /procoder:audit. Whole-repo sweep; use /procoder:review for a diff.
find-dead-code
Find genuinely dead / unused / unreachable SOURCE code - unused functions, classes, methods, exports, and unreachable branches that a linter's local-scope rules miss - with the right whole-program tool for the stack (vulture, knip, go deadcode). Use when the user asks to "find dead code", "remove unused code", "what code is unused", "dead-code scan", or "clean up the codebase" before a refactor or release.
dead-code-finder
Find genuinely unused code — unreferenced exports, unreachable files, and unused dependencies — and remove it safely with build/test verification. Use when trimming a codebase or untangling years of accreted cruft.