skills.rest
cenconq25
cenconq25COMMUNITY
Explore all skills by this author →
GitHub

tech-debt

Scans codebases for TODO/FIXME markers, deprecated APIs, and stale dependencies to maintain a scored debt register.

39|6|Updated May 3, 2026
Search Tags:#planning#technical debt#prioritization#risk-management#code-analysis#scanning
One-click install
npx skills add https://github.com/cenconq25/claude-code-app-studio --skill tech-debt-cenconq25
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/cenconq25/claude-code-app-studio/tree/main/.claude/skills/tech-debt
Command: npx skills add https://github.com/cenconq25/claude-code-app-studio --skill tech-debt-cenconq25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Technical debt accumulates across a codebase, slowing changes and increasing risk. This Skill provides a living debt register, automated indicators, and a plan to pay down debt so teams can ship confidently.

Core Features & Use Cases

  • Debt scanning: identifies TODO, FIXME, deprecated APIs, version skew, dead flags, and stale dependencies across the codebase.
  • Debt register: maintains a central, scored register with impact and effort, and prioritization for repayment.
  • Pay-down planning: proposes sprint-level repayment plans and surfaces actionable work items.
  • Use case: development teams track debt to avoid release blockers and to improve code health over time.

Quick Start

Run a full debt scan to populate or refresh the debt register, then review the prioritized plan for next sprint.

Frequently Asked Questions about tech-debt

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

FAQPage Schema
How do I track technical debt across my codebase effectively?▼

To track technical debt effectively, run a full codebase scan to populate a central register, then review the generated prioritization plan for your next sprint.

What is the best way to prioritize technical debt repayment?▼

The best way to prioritize technical debt repayment is by scoring identified items using impact and effort metrics, which generates an actionable, prioritized pay-down plan for development teams.

Can I automatically scan for deprecated APIs and stale dependencies?▼

Yes, you can automatically scan for deprecated APIs and stale dependencies, alongside TODO markers, FIXME comments, dead flags, and version skew to maintain a live debt register.

How do I plan a sprint to pay down technical debt?▼

You can plan a sprint to pay down technical debt by reviewing the debt register, which proposes sprint-level repayment plans and surfaces actionable work items based on impact and effort scoring.

What types of code issues are categorized as technical debt?▼

Code issues categorized as technical debt include TODO markers, FIXME comments, deprecated APIs, version skew, dead flags, and stale dependencies identified through automated codebase scanning.

Does this technical debt scanning require external dependencies?▼

No, this technical debt scanning requires no external dependencies, operating independently to identify debt markers and maintain a living register within your software engineering workflow.

Related Skills

Explore More Software Engineering Skills→
nguyennd93nguyennd93

tech-debt

Scan codebases for technical debt indicators and generate prioritized reports.

Community
Advanced
li3pli3p

debt-scan

Identify and prioritize technical debt in a codebase for remediation planning.

Community
Intermediate
amanhsnamanhsn

Tech Debt Tracker

Scan codebases to identify, quantify, and prioritize technical debt.

Community
Advanced
troykellytroykelly
11

no-deferred-work

Detect TODO, FIXME, and HACK patterns and enforce immediate action or tracked deferral.

Community
Basic