← ClaudeAtlas

tech-debtlisted

Inventory, measure and prioritize technical debt across a whole repository - aged TODO/FIXME/HACK markers (git blame), suppressed lint/type warnings, churn x complexity hotspots (git log + lizard), duplicated code (jscpd), outdated dependencies, untested modules. Writes and updates a TECH_DEBT.md register with impact, effort and priority, tracks the trend between runs, optionally files GitHub issues, and hands fixes to the refactor skill. Use for technical debt, tech debt audit, code health, debt register, hotspots, legacy code, what to clean up first.
hashgesh/skill-hive · ★ 0 · Code & Development · score 72
Install: claude install-skill hashgesh/skill-hive
# Technical Debt Skill Find where the debt is, rank it by what it costs, and keep a register that shows whether it is shrinking. This skill **measures and plans**; it does not change code. Fixes go to the refactor skill (or the linter skills) one item at a time. ## When Invoked 1. **Scope**: ask which part of the repo to scan (default: the whole repo). Only tracked files count: `rg` and `jscpd` respect `.gitignore`. Also skip vendored, generated and lock files (`vendor/`, `third_party/`, `dist/`, `build/`, `*.min.js`, `*.lock`, `package-lock.json`). 2. **Check tools**: `git` and `rg` are required. `lizard`, `jscpd` and the package managers are optional: skip a scan whose tool is missing, say so in the report, and show its install command. 3. **Run the scans** below. Some tools exit 1 when they *find* something (`lizard -w`, `npm outdated`); that is a result, not an error. 4. **Score every finding** with the rules in Prioritizing. 5. **Write or update `TECH_DEBT.md`** (format below). Show the diff before saving. If the file exists, keep item IDs and statuses, mark items that are gone as `resolved`, and add a row to the trend table. 6. **Summarize** in chat: totals per category, the change since the last run, and the top 5 items to tackle first. 7. **Offer next steps**: fix one item now with the refactor skill, find out why an old `HACK`/`FIXME` exists with the code-history skill, or file issues for the top items (see Issues). Ask before doing any of them. ## Scans ### 1.