tech-debt

Scan repositories for TODO, FIXME, and HACK markers to prioritize technical debt.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill tech-debt-polsegu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/polsegu/Claude-Code-Game-Dev/tree/main/.claude/skills/tech-debt
Command: npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill tech-debt-polsegu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill centralizes discovery and management of technical debt so teams can find, categorize, and schedule fixes instead of letting issues accumulate unnoticed. It reduces the friction of scanning large repositories for TODOs, FIXMEs, hacks, deprecated APIs, duplication, and other debt indicators, and provides a register and prioritization guidance to inform sprint planning.

Core Features & Use Cases

  • Automated Scanning: Locate TODO, FIXME, HACK, @deprecated markers, large files, long functions, and duplicated code to surface potential debt.
  • Directed Entry Management: Add manual debt entries with description, category, affected files, effort estimate, and impact rationale to maintain a human-curated register.
  • Prioritization & Reporting: Score items by impact, frequency, and effort to recommend sprint inclusions, and generate trend reports showing items added, resolved, and aged entries.
  • Use Case: During a sprint review, run a scan to update the debt register, re-prioritize entries by calculated score, and export a report to plan remediation work for the next sprint.

Quick Start

Run the tech-debt skill in scan mode to find TODOs, FIXMEs, HACKs, large files and duplicated code and ask to append the findings to docs/tech-debt-register.md.

Frequently Asked Questions about tech-debt

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

FAQPage Schema
How do I scan my codebase for TODO and FIXME comments to track technical debt?

You can track technical debt by scanning your codebase for TODO, FIXME, and HACK comments, deprecated symbols, duplicated code, and missing tests. The scan requires repository read access to locate these debt indicators across the project files.

What is the best way to prioritize technical debt for sprint planning?

The best way to prioritize technical debt is by scoring items based on impact, frequency, and estimated fix effort using simple heuristics. This generates sprint-ready reports that recommend which debt entries to include for remediation work.

Can I manually add technical debt entries to a debt register?

Yes, you can add manual debt entries to the debt register. Each directed entry can include a description, category, affected files, effort estimate, and impact rationale to maintain a human-curated record alongside automated scan results.

Does tracking technical debt require write access to update repository files?

Tracking technical debt requires repository read access for pattern scanning, but write permission is optional. If granted, write access allows the skill to automatically update docs/tech-debt-register.md with the latest findings.

What types of code quality issues can a technical debt scan detect?

A technical debt scan can detect TODO and FIXME comments, HACK markers, deprecated symbols, large files, long functions, duplicated code, and missing tests. These indicators are categorized to surface potential debt accumulating in the repository.

How do I generate trend reports showing resolved and aged technical debt items?

You can generate trend reports by running a scan to update the debt register and re-prioritize entries. The reports show items added, items resolved, and aged entries over time to inform sprint planning and remediation tracking.