Install any skill in seconds. Free to start, no credit card required.
Get Started Free →qdhenry/remove-dead-code
Safely identifies and removes dead code in TypeScript/JavaScript projects using multi-agent analysis with automatic backup branches.
Passed 13 of 21 test cases with the skill, and 13 of 21 without it.
3 fixed11 passed either way5 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
When a user asks an ambiguous question like 'Can you clean up dead code in my project?', what exact clarifying question should be asked?
| Checked | Without skill | With skill |
|---|---|---|
| Asks the user if they want to scan first | Missed | Passed |
The instructions your model reads when the skill loads.
<essential_principles>
Safety-first dead code removal. Every removal is protected by an automatic backup branch. Multi-agent analysis reduces false positives. No code is deleted without cross-validation.
1. Backup Before Everything
Before any modification, create a timestamped backup branch from the current HEAD. This is non-negotiable. The branch name format is backup/dead-code-removal/{timestamp}.
2. Parallel Scout + Validator Pattern
Multiple scout agents analyze different aspects of dead code in parallel. A validator agent then cross-checks all findings against the full codebase before anything is flagged for removal. Only code confirmed dead by both scouts AND validator gets removed.
3. Conservative by Default
When in doubt, keep the code. False negatives (missing some dead code) are acceptable. False positives (removing live code) are not. Dynamic imports, reflection, test utilities, and public API surface are always treated as potentially live.
4. Never Remove Without Reporting First
The scan workflow produces a report. The user reviews the report. Only then does the remove workflow execute against confirmed items.
</essential_principles>
Wait for response before proceeding.
test cases passed, vs 13 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.