Tech Debt Tracker
Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans.
Before & after
Same prompt, same agent — the only difference is the skill.
Technical debt is something that accumulates in codebases over time. There are various things that could be causing issues - old dependencies, poorly structured code, missing tests, things like that. You might want to do a code review to identify areas that need work. Some codebases have more debt than others depending on how long they've been around and how many people worked on them. Prioritizing what to fix is important. Think about what causes the most problems or slows you down the most. Different teams approach cleanup differently.
TECH DEBT SCAN & PRIORITY MATRIX TOP 3 URGENT (fix this sprint): 1. DEPENDENCY SECURITY (score: 94/100 severity) Oldest vulnerable lib: lodash 3.10.1 (2018, 4 critical CVEs) Affected files: 12 imports across utils/ Fix effort: 4hrs (bump to v4.17.21, check deprecated API usage) Blocked by: None Payoff: Unblocks security audit, removes risk of breach 2. TEST COVERAGE CLIFF (score: 78/100) Payment module: 0% coverage (critical path) 15 test cases needed for stripe-integration.ts Fix effort: 8hrs Blocked by: Need Stripe test API keys Payoff: Confidence for next refactor; catches bugs before production 3. CIRCULAR IMPORTS (score: 64/100) models/User.ts ← → services/AuthService.ts Causes tree-shake failures, increases bundle +47KB Fix effort: 6hrs (extract shared enum) Payoff: Smaller JS, faster cold start MODERATE (next quarter): • Deprecated React lifecycle methods in 2 components (score: 42) • Flaky integration tests (score: 38) • Monolithic service class (score: 31) SCORE METHODOLOGY: Severity × Frequency × Fix-effort trade-off REMEDIATION ROADMAP: Start with dependencies (unblock security), then tests (unblock features), then structure (long-term velocity).
About this skill
name: tech-debt-tracker description: Use when Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans.
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.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the tech-debt-tracker skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Tech Debt Tracker; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: tech-debt-tracker
description: Use when scanning a codebase for technical debt, scoring severity, tracking trends over time, or generating a prioritized remediation plan.
version: 1.0.0
category: Development / Engineering
author: AgentVolt
license: proprietary
tags:
- development
- engineering
---
# Tech Debt Tracker
Scans a codebase for technical debt, scores its severity, tracks trends over time, and generates a prioritized remediation plan, also useful for legacy modernization planning and maintenance-cost estimation.
## When to use
… (sign up to view the full skill)Featured in
More development skills
View all Development skills →Generate
Scaffold code, tests, and boilerplate from a short spec.
Performance Profiler
Systematic performance profiling for Node.js, Python, and Go applications.
Threat Detection
Use when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry.
Agent Harness
Turns a domain folder of skills into a bounded agentic loop: compile a goal into a task plan, execute with the domain's tools, verify every task, retry within a budget.