Tech debt tracker
Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans.
How to use it
Claude Code
- Run the line below. It pulls the whole folder into
~/.claude/skills/tech-debt-tracker, including the files SKILL.md points to. - Describe your job in plain words. Claude Code follows the skill from there.
npx degit alirezarezvani/claude-skills/engineering/skills/tech-debt-tracker#main ~/.claude/skills/tech-debt-trackerFor one project only, change the path to .claude/skills/tech-debt-tracker. This skill also uses debt_inventory.json, debt_priorities.json, debt_YYYY-MM-DD.json — copying SKILL.md alone won't be enough. See the folder on GitHub.
Claude (web or desktop app)
- On this page open ⋯ → Download .md.
- Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
- Pick the file and Save. Claude shows the name and description and runs a security scan.
- Check the skill is switched on.
- Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
- ChatGPT: make a Project and paste it into Instructions.
- Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
- Check which app you pasted it into — the steps above name the right one.
- Some skills need the paid tier of Claude or ChatGPT.
Paste into Claude, ChatGPT or Cursor.
Source of Tech debt tracker
Show the full text88 lines
| name | description |
|---|---|
| tech-debt-tracker | Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans. Use when users mention tech debt, code quality, refactoring priority, debt scoring, cleanup sprints, or code health assessment. Also use for legacy code modernization planning and maintenance cost estimation. |
Tech Debt Tracker
Tier: POWERFUL 🔥
Category: Engineering Process Automation
Expertise: Code Quality, Technical Debt Management, Software Engineering
Overview
Tech debt is one of the most insidious challenges in software development - it compounds over time, slowing down development velocity, increasing maintenance costs, and reducing code quality. This skill provides a comprehensive framework for identifying, analyzing, prioritizing, and tracking technical debt across codebases.
Tech debt isn't just about messy code - it encompasses architectural shortcuts, missing tests, outdated dependencies, documentation gaps, and infrastructure compromises. Like financial debt, it accrues "interest" through increased development time, higher bug rates, and reduced team velocity.
What This Skill Provides
This skill offers three interconnected tools that form a complete tech debt management system:
- Debt Scanner - Automatically identifies tech debt signals in your codebase
- Debt Prioritizer - Analyzes and prioritizes debt items using cost-of-delay frameworks
- Debt Dashboard - Tracks debt trends over time and provides executive reporting
Together, these tools enable engineering teams to make data-driven decisions about tech debt, balancing new feature development with maintenance work.
Quick Start — scan → prioritize → dashboard
All paths relative to this skill folder. The scanner's JSON output feeds the prioritizer directly; dated inventory snapshots feed the dashboard.
1. Scan the codebase
python3 scripts/debt_scanner.py /path/to/codebase --format json --output debt_inventory.json
Emits debt_inventory.json with scan_metadata, summary, debt_items[], file_statistics, and recommendations. Report the summary counts to the user. (Dry run: assets/sample_codebase.)
2. Prioritize the backlog
python3 scripts/debt_prioritizer.py debt_inventory.json --framework wsjf --team-size 6 --sprint-capacity 20 --format json --output debt_priorities.json
Frameworks: cost_of_delay (default), wsjf, rice. Output contains prioritized_backlog (work top-down), sprint_allocation (paste into sprint planning), and insights.
3. Track trends over time
Keep dated snapshots (debt_YYYY-MM-DD.json), then:
python3 scripts/debt_dashboard.py --input-dir snapshots/ --period monthly --format both --output debt_dashboard
Or pass files explicitly (samples: assets/historical_debt_2024-01-15.json assets/historical_debt_2024-02-01.json). The dashboard reports trend direction and executive-ready summaries — use it to verify a cleanup sprint actually reduced debt.
Verification loop
After a remediation sprint: re-run step 1, re-run step 3 with the new snapshot, and assert the targeted categories' counts dropped. A cleanup that doesn't move the dashboard is rework, not debt paydown.
Technical Debt Classification Framework
→ See references/debt-frameworks.md for details (also: references/debt-classification-taxonomy.md, references/prioritization-framework.md, references/stakeholder-communication-templates.md)
Common Pitfalls and How to Avoid Them
1. Analysis Paralysis
Problem: Spending too much time analyzing debt instead of fixing it. Solution: Set time limits for analysis, use "good enough" scoring for most items.
2. Perfectionism
Problem: Trying to eliminate all debt instead of managing it. Solution: Focus on high-impact debt, accept that some debt is acceptable.
3. Ignoring Business Context
Problem: Prioritizing technical elegance over business value. Solution: Always tie debt work to business outcomes and customer impact.
4. Inconsistent Application
Problem: Some teams adopt practices while others ignore them. Solution: Make debt tracking part of standard development workflow.
5. Tool Over-Engineering
Problem: Building complex debt management systems that nobody uses. Solution: Start simple, iterate based on actual usage patterns.
Technical debt management is not just about writing better code - it's about creating sustainable development practices that balance short-term delivery pressure with long-term system health. Use these tools and frameworks to make informed decisions about when and how to invest in debt reduction.
| 1 | |
| 2 | name tech-debt-tracker |
| 3 | description Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans. Use when users mention tech debt, code quality, refactoring priority, debt scoring, cleanup sprints, or code health assessment. Also use for legacy code modernization planning and maintenance cost estimation. |
| 4 | |
| 5 | |
| 6 | # Tech Debt Tracker |
| 7 | |
| 8 | **Tier**: POWERFUL 🔥 |
| 9 | **Category**: Engineering Process Automation |
| 10 | **Expertise**: Code Quality, Technical Debt Management, Software Engineering |
| 11 | |
| 12 | ## Overview |
| 13 | |
| 14 | Tech debt is one of the most insidious challenges in software development - it compounds over time, slowing down development velocity, increasing maintenance costs, and reducing code quality. This skill provides a comprehensive framework for identifying, analyzing, prioritizing, and tracking technical debt across codebases. |
| 15 | |
| 16 | Tech debt isn't just about messy code - it encompasses architectural shortcuts, missing tests, outdated dependencies, documentation gaps, and infrastructure compromises. Like financial debt, it accrues "interest" through increased development time, higher bug rates, and reduced team velocity. |
| 17 | |
| 18 | ## What This Skill Provides |
| 19 | |
| 20 | This skill offers three interconnected tools that form a complete tech debt management system: |
| 21 | |
| 22 | **Debt Scanner** - Automatically identifies tech debt signals in your codebase |
| 23 | **Debt Prioritizer** - Analyzes and prioritizes debt items using cost-of-delay frameworks |
| 24 | **Debt Dashboard** - Tracks debt trends over time and provides executive reporting |
| 25 | |
| 26 | Together, these tools enable engineering teams to make data-driven decisions about tech debt, balancing new feature development with maintenance work. |
| 27 | |
| 28 | ## Quick Start — scan → prioritize → dashboard |
| 29 | |
| 30 | All paths relative to this skill folder. The scanner's JSON output feeds the prioritizer directly; dated inventory snapshots feed the dashboard. |
| 31 | |
| 32 | ### 1. Scan the codebase |
| 33 | |
| 34 | |
| 35 | python3 scripts/debt_scanner.py /path/to/codebase --format json --output debt_inventory.json |
| 36 | |
| 37 | |
| 38 | Emits `debt_inventory.json` with `scan_metadata`, `summary`, `debt_items[]`, `file_statistics`, and `recommendations`. Report the `summary` counts to the user. (Dry run: `assets/sample_codebase`.) |
| 39 | |
| 40 | ### 2. Prioritize the backlog |
| 41 | |
| 42 | |
| 43 | python3 scripts/debt_prioritizer.py debt_inventory.json --framework wsjf --team-size 6 --sprint-capacity 20 --format json --output debt_priorities.json |
| 44 | |
| 45 | |
| 46 | Frameworks: `cost_of_delay` (default), `wsjf`, `rice`. Output contains `prioritized_backlog` (work top-down), `sprint_allocation` (paste into sprint planning), and `insights`. |
| 47 | |
| 48 | ### 3. Track trends over time |
| 49 | |
| 50 | Keep dated snapshots (`debt_YYYY-MM-DD.json`), then: |
| 51 | |
| 52 | |
| 53 | python3 scripts/debt_dashboard.py --input-dir snapshots/ --period monthly --format both --output debt_dashboard |
| 54 | |
| 55 | |
| 56 | Or pass files explicitly (samples: `assets/historical_debt_2024-01-15.json assets/historical_debt_2024-02-01.json`). The dashboard reports trend direction and executive-ready summaries — use it to verify a cleanup sprint actually reduced debt. |
| 57 | |
| 58 | ### Verification loop |
| 59 | |
| 60 | After a remediation sprint: re-run step 1, re-run step 3 with the new snapshot, and assert the targeted categories' counts dropped. A cleanup that doesn't move the dashboard is rework, not debt paydown. |
| 61 | |
| 62 | ## Technical Debt Classification Framework |
| 63 | → See references/debt-frameworks.md for details (also: references/debt-classification-taxonomy.md, references/prioritization-framework.md, references/stakeholder-communication-templates.md) |
| 64 | |
| 65 | ## Common Pitfalls and How to Avoid Them |
| 66 | |
| 67 | ### 1. Analysis Paralysis |
| 68 | **Problem**: Spending too much time analyzing debt instead of fixing it. |
| 69 | **Solution**: Set time limits for analysis, use "good enough" scoring for most items. |
| 70 | |
| 71 | ### 2. Perfectionism |
| 72 | **Problem**: Trying to eliminate all debt instead of managing it. |
| 73 | **Solution**: Focus on high-impact debt, accept that some debt is acceptable. |
| 74 | |
| 75 | ### 3. Ignoring Business Context |
| 76 | **Problem**: Prioritizing technical elegance over business value. |
| 77 | **Solution**: Always tie debt work to business outcomes and customer impact. |
| 78 | |
| 79 | ### 4. Inconsistent Application |
| 80 | **Problem**: Some teams adopt practices while others ignore them. |
| 81 | **Solution**: Make debt tracking part of standard development workflow. |
| 82 | |
| 83 | ### 5. Tool Over-Engineering |
| 84 | **Problem**: Building complex debt management systems that nobody uses. |
| 85 | **Solution**: Start simple, iterate based on actual usage patterns. |
| 86 | |
| 87 | Technical debt management is not just about writing better code - it's about creating sustainable development practices that balance short-term delivery pressure with long-term system health. Use these tools and frameworks to make informed decisions about when and how to invest in debt reduction. |
| 88 |
Discussion
Browse more free Claude skills or everything in Product.