tech-debt

Scan source files for debt markers and generate prioritized tech debt reports.

14|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill tech-debt-euraika-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/Euraika-Labs/Codex-Code-Game-Studios/tree/main/.agents/skills/tech-debt
Command: npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill tech-debt-euraika-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Technical debt accumulates unnoticed in codebases, leading to maintainability issues, hidden bugs, and reduced development velocity. This skill helps teams systematically detect, record, and prioritize that debt.

Core Features & Use Cases

  • Scanning: Automatically searches the repository for common debt markers such as TODO, FIXME, HACK, deprecated APIs, large files, and duplicated code, categorizing findings into architecture, quality, test, documentation, dependency, and performance debt.
  • Register Management: Maintains a markdown debt register (docs/tech-debt-register.md) where new entries can be added manually or updated after prioritization.
  • Prioritization: Calculates priority scores based on impact, frequency, and effort, reorders the register, and recommends items for the next sprint.
  • Reporting: Generates summary statistics and trends to keep stakeholders informed about debt health.

Quick Start

Ask the tech-debt skill to scan the codebase and update the debt register.

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

To track technical debt, scan source files for common markers like TODO, FIXME, and HACK, then calculate priority scores using impact, frequency, and effort metrics to generate a ranked markdown register for your development team.

What types of technical debt can a codebase scan detect?

A codebase scan detects technical debt by searching for TODO, FIXME, HACK markers, deprecated APIs, large files, and duplicated code, categorizing findings into architecture, quality, test, documentation, dependency, and performance debt.

How do I create a technical debt register for sprint planning?

Create a technical debt register by scanning your repository for debt markers, calculating priority scores based on impact, frequency, and effort, and writing the ranked findings to a markdown file to recommend items for the next sprint.

Can I manually add technical debt entries to an existing report?

Yes, you can manually add new technical debt entries to the register, update existing items after prioritization, and re-rank the list to ensure accurate tracking and reporting for stakeholders.

How are technical debt priority scores calculated?

Technical debt priority scores are calculated using three metrics: impact, frequency, and effort, which automatically re-rank the debt register and recommend the highest priority items for development teams to address.