tech-debt

Scan codebases for TODO, FIXME, HACK, and deprecated API markers.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nevesb/idol-agency-maker --skill tech-debt-nevesb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/nevesb/idol-agency-maker/tree/main/.claude/skills/tech-debt
Command: npx skills add https://github.com/nevesb/idol-agency-maker --skill tech-debt-nevesb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Technical debt accumulates as projects evolve, slowing down delivery and increasing risk. This Skill helps teams track, categorize, and prioritize debt across the codebase, turning scattered issues into a structured repayment plan.

Core Features & Use Cases

  • Debt scanning: detects TODO, FIXME, HACK, and deprecated markers; flags long files and long functions; surfaces architecture, code quality, test, documentation, dependency, and performance debt.
  • Debt register maintenance: creates and updates a centralized debt register with priority, affected files, and sprint targets.
  • Prioritization & scheduling: provides a formulaic approach to rank debt items and plan resolutions in upcoming sprints.

Quick Start

Run the tech-debt workflow to scan the repository for debt indicators and update the debt register.

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 a codebase?

Track technical debt by scanning your codebase for TODO, FIXME, HACK markers, deprecated APIs, and long functions. This process maintains a centralized debt register that categorizes issues across architecture, code quality, tests, and documentation for structured repayment.

What is the best way to prioritize technical debt for upcoming sprints?

Prioritize technical debt using a formulaic approach that ranks items based on priority, affected files, and sprint targets. The prioritization workflow evaluates scanned debt items to help teams plan structured resolutions in upcoming development cycles.

Can I scan for deprecated APIs and long functions in codebases of any size?

Yes, scanning for deprecated APIs, long files, and long functions applies to codebases of all sizes. The workflow detects these markers alongside TODO, FIXME, and HACK flags to surface architecture, performance, and dependency debt comprehensively.

How do I create a centralized technical debt register?

Create a centralized technical debt register by running the scan and add subcommands. This workflow identifies code quality issues, logs them with priority levels and affected files, and maintains the register for continuous prioritization and reporting.

What types of technical debt can I detect beyond code quality issues?

Beyond code quality issues, you can detect architecture, test, documentation, dependency, and performance technical debt. The scanner identifies TODO, FIXME, HACK markers, deprecated APIs, long files, and long functions to provide comprehensive codebase coverage.

Does tracking technical debt require any specific dependencies or components?

No, tracking technical debt requires no external dependencies or components. The workflow operates deterministically using scan, add, prioritize, and report subcommands to maintain the debt register without additional environment setup.