tech-debt

Scan codebases for technical debt indicators and generate a prioritized debt register.

Updated Apr 8, 2026

Search Tags:#refactoring #prioritization #code-quality #scanning #technical-debt #debt-register

Ready to run

npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill tech-debt-hechaoyannet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/HechaoYannet/3kingdom-unity/tree/main/.claude/skills/tech-debt
Command: npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill tech-debt-hechaoyannet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track, categorize, and prioritize technical debt across the codebase to prevent erosion and improve long-term maintainability.

Core Features & Use Cases

Debt discovery: scans for indicators like TODO, FIXME, HACK, deprecated markers, and large functions to surface hidden debt.
Debt register: maintains a centralized debt register with categories, affected files, and estimated effort.
Prioritization & planning: suggests remediation order and aligns with sprint planning to optimize ROI.
Reporting & remediation: generates summaries and actionable tasks for developers and QA.

Quick Start

Run a debt scan to generate the current debt register for the repository.

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 across my codebase?▼

Scanning a codebase for indicators like TODO, FIXME, and large functions surfaces hidden technical debt. It generates a centralized debt register with categories, affected files, and estimated effort for remediation planning.

What is the best way to identify hidden technical debt for sprint planning?▼

Scanning for deprecated markers, duplications, and long methods identifies hidden technical debt. This approach suggests a remediation order and aligns actionable tasks with sprint planning to optimize return on investment.

Can I generate a debt register for multiple repositories and programming languages?▼

Yes, technical debt scanning is applicable across multiple languages and repositories. It maintains a centralized debt register that includes categories, affected files, and estimated effort for ongoing maintenance and risk assessment.

How does automated technical debt tracking handle risk categorization and remediation scheduling?▼

Automated technical debt tracking handles risk categorization by evaluating scanned indicators and estimating effort. It generates actionable remediation tasks and recommended fixes, scheduling them to optimize return on investment during maintenance.

When should I scan my codebase to assess technical debt and maintain code quality?▼

You should scan your codebase during ongoing maintenance, sprint planning, and risk assessment. Regular scanning prevents code quality erosion by surfacing hidden debt and generating actionable tasks for developers and QA.