skills.rest
Rohithdgrr
RohithdgrrCOMMUNITY
Explore all skills by this author →
GitHub

tech-debt-tracker

Scan codebases for technical debt, prioritize remediation, and track debt trends over time.

Updated Aug 14, 2026
Search Tags:#code quality#refactoring#technical debt#prioritization#sprint planning#code health#wsjf
One-click install
npx skills add https://github.com/Rohithdgrr/REEK-uninstaller --skill tech-debt-tracker-rohithdgrr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt-tracker
Source: https://github.com/Rohithdgrr/REEK-uninstaller/tree/main/.opencode/skills/tech-debt-tracker
Command: npx skills add https://github.com/Rohithdgrr/REEK-uninstaller --skill tech-debt-tracker-rohithdgrr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Engineering teams accumulate technical debt that silently slows development velocity and increases maintenance costs, but they lack a systematic way to identify, quantify, and prioritize it. This Skill turns vague concerns about code quality into a scored, prioritized backlog with trend tracking so teams can make data-driven decisions about when to pay down debt. ## Core Features & Use Cases - Debt Scanner: Automatically detects debt signals in a codebase (large functions, high complexity, duplicate code, TODO comments, security risks) and emits a structured JSON inventory with severity scores and recommendations. - Debt Prioritizer: Scores each debt item using cost-of-delay, WSJF, or RICE frameworks, estimates effort and interest rates, and produces a sprint-by-sprint allocation plan. - Debt Dashboard: Compares dated inventory snapshots to compute health scores, trend direction, debt velocity (accruing vs. resolved), and executive-ready summaries. - Use Case: Before a cleanup sprint, scan the repository, prioritize the backlog with WSJF for a 6-person team, then after the sprint re-scan and run the dashboard to verify the targeted debt categories actually decreased. ## Quick Start Ask the AI to scan your codebase for technical debt and generate a prioritized remediation plan with sprint allocation.

Frequently Asked Questions about tech-debt-tracker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan a codebase for technical debt?▼

Run the debt scanner script against your repository root to produce a JSON inventory containing debt items, severity scores, file statistics, and recommendations. The output feeds directly into the prioritizer for backlog ranking.

How do I prioritize technical debt for sprint planning?▼

Pass the scanner's JSON inventory to the prioritizer with your team size and sprint capacity. It scores items using cost-of-delay, WSJF, or RICE frameworks and outputs a sprint-by-sprint allocation plan you can paste into sprint planning.

Which prioritization framework should I use for tech debt?▼

Cost-of-delay is the default and works well for general backlogs. WSJF suits SAFe-oriented teams balancing business value against job size, while RICE fits product-driven teams weighing reach, impact, and confidence against effort.

How do I track whether a cleanup sprint reduced technical debt?▼

Keep dated JSON snapshots from each scan, then run the dashboard over the snapshot directory. It computes health score trends and debt velocity, so you can verify the targeted categories' counts actually dropped after the sprint.

What types of technical debt can be detected automatically?▼

The scanner detects code-level signals like large functions, high cyclomatic complexity, duplicate code, long lines, missing docstrings, TODO comments, and security risks. Architecture, test, documentation, dependency, and infrastructure debt are classified via the reference taxonomy.

What are the limitations of automated tech debt scoring?▼

Automated scores are estimates based on debt type and severity heuristics, not precise measurements. Architecture-level debt and business context require human judgment, so treat the output as a starting backlog rather than a definitive plan.

Related Skills

Explore More Software Engineering Skills→
geoywsgeoyws
2

rcheckout

Recursively check out a git branch across root repository and nested submodules.

Community
Intermediate
ronniepinnellronniepinnell

sprint

Review backlog items and prioritize work for upcoming sprints.

Community
Intermediate
KingInYellowsKingInYellows

debt-conventions

Define unified debt scoring frameworks and JSON output schemas for scanner agents.

Official
Advanced
KoryakinYurijKoryakinYurij

skill-evals

Build automated evaluation suites with code-based and LLM-as-judge graders.

Community
Advanced