skills.rest
mcouthon
mcouthonCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

tech-debt

Identify, catalog, and eliminate technical debt across codebases.

77|11|Updated Dec 26, 2025
Search Tags:#refactor#code-quality#static-analysis#dead-code#technical-debt#todo-management
One-click install
npx skills add https://github.com/mcouthon/agents --skill tech-debt-mcouthon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/mcouthon/agents/tree/main/.github/skills/tech-debt
Command: npx skills add https://github.com/mcouthon/agents --skill tech-debt-mcouthon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify, catalog, and eliminate technical debt in a codebase, improving maintainability and long-term velocity.

Core Features & Use Cases

  • Debt indicators to detect: TODO/FIXME, HACK, dead code, unused imports, long functions, and risky anti-patterns.
  • Prioritization and planning: Quick wins vs longer-term refactors with risk assessment and testing requirements.
  • Safe deletion and refactoring: Guidelines to ensure changes are test-covered and reversible.
  • Debt reporting: Structured summaries and remediation plans to track progress across sessions.

Quick Start

Run a debt-health pass across the repository to identify TODOs, dead code, and complexity hotspots.

Frequently Asked Questions about tech-debt

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

FAQPage Schema
How do I identify and catalog technical debt in a codebase?▼

To identify technical debt, run a debt-health pass to detect TODOs, FIXMEs, HACK comments, dead code, unused imports, and complexity hotspots, generating structured summaries and remediation plans to track progress across sessions.

What is the best way to prioritize refactoring tasks when cleaning up technical debt?▼

Prioritize refactoring by categorizing debt into quick wins versus longer-term refactors, applying risk assessment and evaluating automated testing requirements to ensure safe and traceable remediation steps.

Do I need automated testing coverage before removing dead code and unused imports?▼

Yes, automated testing coverage is required for safe deletion and refactoring. Adhering to safe deletion patterns ensures changes are test-covered and reversible, minimizing regressions when removing dead code.

Can I use this technical debt tracking approach for projects of any size and language?▼

Yes, this technical debt tracking approach applies to projects of any size and language. It guides debt discovery, prioritization, safe fixes, and documentation comprehensively across the entire development lifecycle.

What are the limitations of refactoring technical debt without traceable remediation steps?▼

Without traceable remediation steps and automated testing, safe deletion patterns are broken, significantly increasing the risk of regressions and making it difficult to track remediation progress across development sessions.

Related Skills

Explore More Software Engineering Skills→
BerryKuipersBerryKuipers
7

record-quality-baseline

Record code quality metrics before refactoring into a timestamped JSON baseline.

Community
Intermediate
CloudChefCloudChef
15

cost-optimization

Analyze SmartCMP findings and execute native day2 remediations.

Official
Advanced
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced
tranhieutttranhieutt
70

tech-debt

Scan codebase markers and update the technical debt register.

Community
Advanced