tech-debt-tracker
Scan codebases for technical debt with AST parsing, prioritize by impact, and generate trend dashboards
Install / Use
npx skills add borghei/Claude-Skills --skill tech-debt-trackerInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Project & Program ManagementSupported Platforms
Tags
Our assessment of tech-debt-tracker
tech-debt-tracker scores 81/100 on our quality scale, 68th of 82 Project & Program Management skills we index.
Its SKILL.md is 7.6 KB long, well organised into 8 sections and no code examples: a thorough specification that gives an agent plenty to work with.
It has 817 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so tech-debt-tracker is actively maintained.
- Our last check on 2026-11-08 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-08. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
tech-debt-tracker compared with similar skills
All 4 of these similar skills score higher than tech-debt-tracker; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| tech-debt-tracker (this skill)by borghei | 81 | 817 | 57d ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 4d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 56d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 56d ago | SKILL.md |
| prospectingby coreyhaines31 | 100 | 60.1k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install tech-debt-tracker?
- Run
npx skills add borghei/Claude-Skills --skill tech-debt-tracker. The install tabs above show the steps for each supported agent. - Which AI agents does tech-debt-tracker work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is tech-debt-tracker safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is tech-debt-tracker still maintained?
- The repository was last updated about 2 months ago, so tech-debt-tracker is actively maintained.
Skill content
View source on GitHubname: tech-debt-tracker description: > Scan codebases for technical debt with AST parsing, prioritize by impact, and generate trend dashboards. Use when tracking tech debt, prioritizing refactoring, calculating cost-of- delay, planning sprint debt, or reporting debt to execs. license: MIT + Commons Clause metadata: version: 1.1.0 author: borghei category: engineering domain: code-quality tier: POWERFUL updated: 2026-06-17
Tech Debt Tracker
The agent identifies, scores, prioritizes, and tracks technical debt across codebases using AST parsing, cost-of-delay analysis, and trend dashboards.
Core Capabilities
- Detection — AST parsing (Python) and regex pattern matching (all languages) across six debt categories: code, architecture, test, documentation, dependency, infrastructure.
- Severity scoring — rate each item on velocity, quality, productivity, and business impact (1-10) plus effort sizing (XS-XL) and risk.
- Cost-of-delay — compute interest rate (
Impact x Frequency) and cost of delay (Interest x Sprints x Team Multiplier); also WSJF and RICE frameworks. - Prioritization — plot on the Cost-of-Delay vs Effort matrix (Immediate / Planned / Opportunistic / Backlog).
- Sprint allocation — apply the Debt-to-Feature ratio by team velocity; reserve capacity for debt work.
- Refactoring strategies — Strangler Fig, Branch by Abstraction, Feature Toggles, Parallel Run.
- Reporting — executive and engineering dashboards, trend analysis, velocity tracking, and forecasts from scan snapshots.
When to Use
- Tracking and quantifying technical debt across a repository.
- Prioritizing refactoring work and calculating cost-of-delay.
- Planning sprint capacity allocation between debt and features.
- Reporting debt health, trends, and investment recommendations to execs.
Clarify First
Before scanning or reporting, confirm these inputs. If any is unknown or vague, ASK — do not assume:
- [ ] Target codebase — the directory to scan (the subject of the debt inventory)
- [ ] Prioritization framework & team size — cost-of-delay / WSJF / RICE and headcount (
--framework,--team-size; changes the ranking and sprint allocation) - [ ] Report audience — exec dashboard vs engineering inventory (sets the report format and altitude)
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
Tools
| Tool | Purpose | Command |
|------|---------|---------|
| debt_scanner.py | Scan a directory for debt signals; output JSON inventory + text report | python scripts/debt_scanner.py <dir> --output scan_results --format both |
| debt_prioritizer.py | Enrich inventory with cost-of-delay/WSJF/RICE and sprint allocation | python scripts/debt_prioritizer.py scan_results.json --framework wsjf --team-size 8 |
| debt_dashboard.py | Trend analysis, velocity, forecasts, and exec summary across snapshots | python scripts/debt_dashboard.py --input-dir ./debt_scans/ --period quarterly |
References
Load the reference that matches the task — keep this file lean and pull detail on demand:
- references/methodology.md — the 7-step workflow, debt-classification table, severity scoring framework, interest-rate/cost-of-delay formulas, prioritization matrix, WSJF, sprint allocation ratios, the debt-item JSON schema, refactoring strategies, and quarterly planning. Read when scoring, prioritizing, or planning.
- references/tool-reference.md — full parameter tables, examples, and output-format details for all three scripts plus the troubleshooting table. Read when running the scripts or debugging output.
- references/dashboards-and-examples.md — executive and engineering dashboard layouts, a worked Python-microservice scan example, and the success-criteria bar. Read when generating reports or validating quality.
- references/debt-classification-taxonomy.md — comprehensive taxonomy for classifying debt across dimensions with detection heuristics per category. Read when calibrating detection or labeling items.
- references/prioritization-framework.md — deep prioritization approaches based on business value, risk, effort, and strategic alignment. Read when designing a prioritization rubric.
- references/stakeholder-communication-templates.md — templates and guidelines for communicating debt status, impact, and recommendations to different stakeholder groups. Read when reporting to execs or product.
Also see the skill-root REFERENCE.md for the Technical Debt Quadrant (Fowler) and the implementation roadmap phases.
Scope & Limitations
This skill covers:
- Static detection of code-level, architecture, test, documentation, dependency, and infrastructure debt via AST parsing (Python) and regex pattern matching (all languages).
- Quantitative prioritization of debt items using cost-of-delay, WSJF, and RICE frameworks with configurable team size and sprint capacity.
- Historical trend analysis, health scoring, debt velocity tracking, and executive/engineering dashboard generation from multiple scan snapshots.
- Sprint allocation planning with capacity-aware backlog scheduling and effort estimation by debt type.
This skill does NOT cover:
- Runtime performance profiling or production monitoring -- see
engineering/performance-profilerandengineering/observability-designerfor those concerns. - Dependency vulnerability scanning (CVE detection) or software composition analysis -- see
engineering/dependency-auditorfor security-focused dependency review. - Automated refactoring or code transformation -- the skill identifies and prioritizes debt but does not modify source code.
- Database schema debt, API contract drift, or infrastructure-as-code drift detection -- see
engineering/database-schema-designer,engineering/api-design-reviewer, andengineering/migration-architectfor those domains.
Integration Points
| Skill | Integration | Data Flow |
|-------|-------------|-----------|
| engineering/dependency-auditor | Feed dependency audit findings into the scanner as dependency_debt items to unify all debt in one inventory. | Dependency audit JSON -> scanner config or manual merge into debt_inventory.json |
| engineering/performance-profiler | Correlate performance hotspots with high-complexity debt items to prioritize refactoring that yields both quality and speed gains. | Profiler hotspot report -> cross-reference with scanner output by file path |
| engineering/ci-cd-pipeline-builder | Add debt_scanner.py as a CI pipeline step to fail builds when health score drops below a threshold or critical debt count increases. | Scanner JSON output -> CI gate condition on summary.health_score |
| engineering/pr-review-expert | Surface relevant debt items during code review by querying the debt inventory for files touched in a pull request. | PR changed-files list -> filter debt_inventory.json by file_path |
| engineering/observability-designer | Map infrastructure debt items (missing monitoring, env inconsistencies) to observability gaps identified by the observability skill. | Dashboard category_distribution -> observability gap analysis |
| engineering/migration-architect | Use the prioritized backlog to scope and sequence large-scale migration efforts, especially for architecture-category debt rated as planned initiatives. | Prioritizer sprint_allocation -> migration planning timeline |
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
prospecting
60.1kWhen the user wants to find and qualify prospects for outbound, or asks who to target first, which signal to prioritize, or where to spot buyers with the problem: buying signals, enrichment, verification, account research.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
