tech-debt

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling.

Core Features & Use Cases

  • Scan for debt indicators: TODO, FIXME, HACK, @deprecated markers, duplicated code, long files, and long functions.
  • Classify debt into categories: Architecture Debt, Code Quality Debt, Test Debt, Documentation Debt, Dependency Debt, and Performance Debt.
  • Maintain a debt register with suggested repayment scheduling and sprint planning.

Quick Start

Run a scan to identify debt indicators across the repository and generate the debt register for review.

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

To track technical debt, scan your codebase for indicators like TODO, FIXME, and HACK markers, then categorize findings into architecture, code quality, and test debt to prioritize repayment in a debt register.

What is the best way to scan for code quality issues and deprecated patterns?

Scanning for code quality issues involves detecting deprecated patterns, duplicated code, and long functions, which are then classified into categories like dependency and performance debt to assess overall codebase health.

Can I generate a debt register for sprint planning from TODO and FIXME markers?

Yes, you can generate a debt register by recording scanned TODO and FIXME markers with their affected files and estimated effort, outputting a structured report suitable for direct sprint planning and repayment scheduling.

How do I categorize technical debt into architecture and performance debt?

Categorize technical debt by scanning for specific code indicators and classifying them into architecture, code quality, tests, docs, dependencies, or performance debt based on the affected files and identified patterns.

Does technical debt scanning work for large codebases with long functions and duplicated code?

Yes, technical debt scanning is designed for large codebases, effectively identifying long files, duplicated code blocks, and long functions to maintain a comprehensive debt register for ongoing quality management.