skills.rest
easonlao
easonlaoCOMMUNITY
Explore all skills by this author →
GitHub

tech-debt

Scan codebases for debt indicators and maintain a prioritized register.

Updated Apr 25, 2026
Search Tags:#documentation#refactoring#maintainability#technical debt#prioritization#sprint planning#code scanning
One-click install
npx skills add https://github.com/easonlao/jiazi-game --skill tech-debt-easonlao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/easonlao/jiazi-game/tree/main/.claude/skills/tech-debt
Command: npx skills add https://github.com/easonlao/jiazi-game --skill tech-debt-easonlao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of technical debt becoming invisible, untracked, and harder to repay over time by turning scattered issues into a prioritized, living register.

Core Features & Use Cases

  • Debt detection & categorization: Scans for TODO/FIXME/HACK, deprecated markers, duplicated patterns, and likely complexity hotspots (large files/functions), then assigns each finding a category such as Architecture, Code Quality, Test, Documentation, Dependency, or Performance.
  • Debt register management: Supports manually adding entries, re-prioritizing the register with a transparent scoring formula, and generating a sprint-ready report.
  • Decision support for repayment: Produces a prioritized list based on impact, frequency of encounter, and estimated fix effort, and flags older items that need conscious acceptance or resolution.

Quick Start

Run the tech-debt scan to find TODO/FIXME/HACK and complexity hotspots, then choose whether to write the findings into 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 track and prioritize technical debt in my codebase?▼

Track technical debt by scanning codebases for TODO, FIXME, and complexity hotspots, then maintaining a structured debt register with category-based scoring to prioritize repayment during sprint planning.

What is the best way to find technical debt indicators like TODO and HACK markers?▼

Finding technical debt indicators requires scanning the codebase for TODO, FIXME, HACK, deprecated markers, and duplicated patterns, then categorizing each finding into Architecture, Code Quality, Test, or Documentation debt.

How do I generate a sprint-ready report for technical debt repayment?▼

Generate a technical debt report by re-prioritizing the register with a transparent scoring formula based on impact, encounter frequency, and estimated fix effort, producing a sprint-ready list for backlog grooming.

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

Yes, you can manually add entries to the technical debt register to track scattered issues, ensuring temporary fixes and growing complexity are documented with explicit confirmation before modifying docs.

How does the scoring formula work for prioritizing technical debt?▼

The scoring formula prioritizes technical debt by evaluating impact, frequency of encounter, and estimated fix effort, assigning each item a category score while flagging older items for conscious acceptance.

Does the technical debt scan automatically write findings into repository documentation?▼

No, the technical debt scan requires explicit user confirmation before writing findings into docs/tech-debt-register.md, applying guardrails to ensure safe modification of repository documentation during maintenance.

Related Skills

Explore More Software Engineering Skills→
emcconnellemcconnell

tech-debt

Scan codebases for technical debt markers and prioritize a markdown debt register.

Community
Intermediate
s3nex-coms3nex-com

technical-debt-tracker

Identify and quantify technical debt across a codebase for remediation planning.

Community
Advanced
LeKayLeKay

tech-debt

Scan codebases for technical debt indicators and maintain a debt register.

Community
Advanced
HomericIntelligenceHomericIntelligence
18

detect-code-smells

Detect code smells and complexity issues in codebases.

Official
Intermediate