tech-debt

Name: tech-debt
Availability: InStock
Author: donchitos

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

23.7k|3.4k|Updated Feb 12, 2026

Search Tags:#code quality #refactoring #maintenance #developer productivity #tech debt #code scanning

Ready to run

npx skills add https://github.com/Donchitos/Claude-Code-Game-Studios --skill tech-debt-donchitos

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/tech-debt
Command: npx skills add https://github.com/Donchitos/Claude-Code-Game-Studios --skill tech-debt-donchitos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps development teams identify, track, categorize, and prioritize technical debt within their codebase, enabling proactive management and reduction.

Core Features & Use Cases

Automated Scanning: Detects common indicators of technical debt like TODOs, FIXMEs, large files/functions, and code duplication.
Debt Register: Maintains a centralized Markdown file (docs/tech-debt-register.md) to log and track all identified debt items.
Prioritization: Scores debt items based on impact and effort, recommending which items to address next.
Reporting: Generates summary reports on the state of technical debt, including trends and aging items.
Use Case: A team can run /tech-debt scan at the start of a sprint to identify new debt, then use /tech-debt prioritize to decide which items to tackle in the current sprint.

Quick Start

Run the tech-debt skill to scan the codebase for technical debt indicators.

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 categorize technical debt in my codebase?▼

You can track technical debt by scanning your codebase for indicators like TODOs and large files, then logging them into a centralized Markdown register. This approach categorizes debt into architectural, code quality, test, and performance domains for proactive management.

What is the best way to prioritize technical debt repayment for a sprint?▼

The best way to prioritize technical debt repayment is by scoring identified items based on their impact and effort. This generates a prioritized recommendation list, helping teams decide exactly which debt items to tackle during the current sprint.

How does automated code scanning detect technical debt indicators?▼

Automated code scanning detects technical debt indicators by searching for common annotations and structural issues. It identifies TODOs, FIXMEs, code duplication, and large files or functions, maintaining a categorized register for tracking.

Do I need specific file system tools to run a technical debt scan?▼

Yes, you need glob, grep, and write tools to perform file system operations and text manipulation. These tools allow the scanner to search the codebase for debt indicators and automatically write the results to a Markdown register.

Can I generate reports on technical debt trends and aging items?▼

Yes, you can generate summary reports on the state of your technical debt, including trends and aging items. This reporting feature helps development teams monitor debt accumulation and evaluate the effectiveness of their maintenance efforts.