techdebt
/techdebt
Detect technical debt — duplicated code, dead code, TODOs, and oversized functions across the codebase. Use at the end of a session or when auditing code hygiene. Trigger on "find tech debt", "any dead code", "duplicated code", "code hygiene", "techdebt".
- Author
- matteocervelli ↗
- Repository
- llms ↗
- Licence
- MIT
- Last repository change
- 21.05.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 21.05.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/scan.sh
What it does and when to use it
Detect technical debt — duplicated code, dead code, TODOs, and oversized functions across the codebase. Use at the end of a session or when auditing code hygiene. Trigger on "find tech debt", "any dead code", "duplicated code", "code hygiene", "techdebt".
Triggers from the description
Original author description
Detect technical debt — duplicated code, dead code, TODOs, and oversized functions across the codebase. Use at the end of a session or when auditing code hygiene. Trigger on "find tech debt", "any dead code", "duplicated code", "code hygiene", "techdebt".
How it works
- Purpose
- Quick Start
- How to Run
- Output Format
- Tool Reference
- Gotchas
SKILL.md preview
--- name: techdebt description: Detect technical debt — duplicated code, dead code, TODOs, and oversized functions across the codebase. Use at the end of a session or when auditing code hygiene. Trigger on "find tech debt", "any dead code", "duplicated code", "code hygiene", "techdebt". allowed-tools: Read, Bash, Grep, Glob --- # Tech Debt Finder ## Purpose Surface technical debt patterns before they accumulate: duplicates, dead code, complexity hotspots, TODOs, oversized files. ## Quick Start ```bash /techdebt # scan current directory /techdebt src/ # scan specific path /techdebt --duplicates # only duplicate check /techdebt --todos # only TODO/FIXME markers /techdebt --dead-code # only dead code ``` ## How to Run Execute the scan script — it auto-detects Python/JS/TS and skips missing tools: ```bash bash $CLAUDE_SKILL_DIR/scripts/scan.sh [path] [filter-flag] ``` Then **interpret and report** the output using the Output Format below. The script handles tool invocation; your job is to classify findings by severity and suggest fixes. ## Output Format Produce a `# Tech Debt Report` with: 1. **Summary table** — category, count, severity (Low / Medium / High) 2. **Details per category** — file, line, symbol, suggestion 3. **Quick Fixes** — any automatable repairs (`ruff --fix`, `eslint --fix`) 4. **Recommended Actions** — prioritized: Immediate / This week / Backlog Severity thresholds: duplicates (Low ≤2, Medium 3-5, High >5), dead code (Low ≤5, High >10), large functions (Medium >75 lines, High >100), large files (High >1000 lines), complexity CC >10 (Medium). ## Tool Reference Tools the script uses (installed = runs; missing = skipped with note): | Check | Python | JS/TS | | ---------------- | ---------------- | ------------ | | Duplicates | pylint | jscpd | | Dead code | vulture | ts-prune | | Complexity/size | radon | eslint | | Circular imports | pycycle | madge | | TODOs | grep (no dep) | grep (no dep)| Install missing tools: `uv add --dev vulture radon pylint` / `npm install -D jscpd ts-prune madge` ## Gotchas - `.venv`, `node_modules`, `dist`, `__pycache__` are auto-excluded by the scan script - `pylint --enable=duplicate-code` is slow on large codebases; warn if scanning >500 files - `ts-prune` only works from the project root (needs `tsconfig.json`); run from a sub-path → 0 findings - `radon cc` = per-function cyclomatic complexity; `radon raw` = per-file LOC — different output formats - Deprecated registry dependency check requires `~/.claude/docs/development/registry.yaml`; skip silently if absent
Files in this package (2)
- SKILL.md 3 KB
- scripts/scan.sh 4 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · matteocervelli/llms | 100 | MIT |
| cardene777/agent-shuriken | 100 | MIT |
| oliver-kriska/claude-elixir-phoenix | 100 | MIT |
| ramonclaudio/skills | 100 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version bc37f392e3de (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100phx-techdebt
Analyze Elixir/Phoenix technical debt — duplicates, refactoring; Use when asked about code quality, cleanup, or what… - 100tech-debt
Use when finding code smells, auditing TODOs, removing dead code, cleaning up unused imports, or assessing code quality. Triggers on: 'use tech-debt mode', 'tech debt', 'code smells', 'clean up', 'remove dead code', 'delete unused', 'simplify'. Full access mode - can modify files and run tests. - 100phx-techdebt
Analyze Elixir/Phoenix technical debt — duplicates, refactoring opportunities, credo issues. Use when asked about code quality, cleanup, or what to improve. - 100doncheli-tech-debt
Identify, quantify, and prioritize technical debt in the codebase. Activate when user mentions "tech debt", "code quality", "technical debt", "code smells", "refactor candidates", "what to clean up". - 100tech-debt
Identify, document, score, and prioritize technical debt into an actionable backlog. Use when: tech debt, code smell, TODO, FIXME, legacy, refactor backlog, quality decay, debt. - 100code-refactoring-tech-debt
Technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Use when auditing a codebase for technical debt or planning remediation.