Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →code-yeongyu/remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits. Triggers: remove dead code, dead code, cleanup, remove unused.
Passed 12 of 17 test cases with the skill, and 9 of 17 without it.
and 7 more in the full report
7 fixed9 passed either way4 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
What primary command should be executed first during static analysis to collect unused TypeScript variables, parameters, and types without writing build output?
| Checked | Without skill | With skill |
|---|---|---|
| Executes bunx tsc --noEmit --noUnusedLocals --noUnusedParameters for the initial scan. | Missed | Passed |
The instructions your model reads when the skill loads.
Dead code removal via massively parallel deep agents. You are the ORCHESTRATOR — you scan, verify, batch, then delegate ALL removals to parallel agents.
Run ALL of these in parallel:
TypeScript strict mode (your primary scanner — run this FIRST):
bunx tsc --noEmit --noUnusedLocals --noUnusedParameters 2>&1
This gives you the definitive list of unused locals, imports, parameters, and types with exact file:line locations.
Explore agents (fire ALL simultaneously as background):
task(subagent_type="explore", run_in_background=true, load_skills=[],
description="Find orphaned files",
prompt="Find files in src/ NOT imported by any other file. Check all import statements. EXCLUDE: index.ts, *.test.ts, entry points, .md, packages/. Return: file paths.")
task(subagent_type="explore", run_in_background=true, load_skills=[],
test cases passed, vs 9 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.