Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →notque/code-cleanup
Detect stale TODOs, unused imports, and dead code.
Passed 9 of 17 test cases with the skill, and 4 of 17 without it.
and 8 more in the full report
7 fixed5 passed either way10 still failing0 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.
We have 10 Python functions flagged for missing type annotations. Which category tier do these belong to and how long will fixing them take?
| Checked | Without skill | With skill |
|---|---|---|
| Categorizes missing type annotations in the Polish tier. | Passed | Passed |
| Estimates remediation time between 10 and 20 minutes per function. | Missed | Passed |
The instructions your model reads when the skill loads.
Scan repositories for 9 categories of technical debt (TODOs, unused imports, dead code, missing type hints, deprecated functions, naming inconsistencies, high complexity, duplicate code, missing docstrings), prioritize findings by impact/effort ratio with time estimates, and generate structured markdown reports with exact file:line references. Can apply safe auto-fixes when the user grants explicit permission.
Focused cleanup -- User says "Clean up the API handlers in src/api/". Read project config, scan src/api/ for all 9 categories, prioritize (5 unused imports auto-fixable, 2 stale TODOs >90d, 1 high-complexity function), present tiered report with auto-fix commands.
Broad debt scan -- User says "What's the state of technical debt in this repo?". Identify languages and source directories, run all applicable scans, group 47 findings into Quick Wins (12), Important (8), Polish (27), generate full report with effort estimates: 2h quick wins, 6h important, 4h polish.
Auto-fix request -- User says "Fix all the unused imports and sort them". Verify ruff/goimports available, scan for F401 and I001 violations only, report 23 unused imports across 8 files, user confirms, apply fixes, run tests, show diff.
| Signal | Load These Files | Why |
|---|---|---|
| writing the cleanup report | report-template.md | Loads detailed guidance from report-template.md. |
| running per-language scans: unused imports, dead code, debug statements | scan-commands.md | Loads detailed guidance from scan-commands.md. |
| checking which cleanup tools are installed per language | tools.md | Loads detailed guidance from tools.md. |
Goal: Determine what to scan and verify tooling is available.
Step 1: Read project context
Step 2: Determine scan scope
Step 3: Verify tool availability
test cases passed, vs 4 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.