tech-debt

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

33|8|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/TraftG/opencode-game-studio --skill tech-debt-traftg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/TraftG/opencode-game-studio/tree/main/.opencode/skills/tech-debt
Command: npx skills add https://github.com/TraftG/opencode-game-studio --skill tech-debt-traftg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track and reduce technical debt across codebases by systematically identifying, registering, and triaging debt items.

Core Features & Use Cases

  • Scan codebases for debt indicators (TODO, FIXME, HACK, deprecated markers) and surface debt types.
  • Maintain a centralized Debt Register with categorization, effort estimates, and prioritization hints.
  • Add manual debt entries and generate sprint-ready plans to schedule repayments.

Quick Start

Run the tech-debt scan to populate the debt register and begin prioritizing fixes.

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 quantify technical debt across a multi-language codebase?

To track technical debt across multiple languages, this tool scans the codebase for indicators like TODO and FIXME, categorizing findings into architecture, code quality, and performance debt within a structured register.

What is the best way to prioritize tech debt repayment for sprint planning?

The best way to prioritize tech debt for sprint planning is to use a centralized debt register that categorizes items, adds effort estimates, and generates a concise sprint-ready report for actionable repayment scheduling.

Can I manually add technical debt entries alongside automated scanning results?

Yes, you can manually add technical debt entries to the register. This allows teams to combine automated scanning results for indicators like HACK and deprecated markers with manually identified architecture or documentation debt.

Does this tech debt scanning tool work with multiple programming languages and projects?

Yes, the tech debt scanning tool applies across multiple languages and projects. It surfaces various debt types including test, dependency, and performance debt without requiring specific language dependencies.

How do I identify performance and architecture debt indicators in my code?

You identify performance and architecture debt by scanning the codebase for specific markers like HACK and FIXME. The tool organizes these findings into a structured debt register for clear categorization.

When should I use a debt register over manual code reviews for tracking tech debt?

Use a debt register when you need to systematically track and triage technical debt across codebases. It enforces clear debt entries and provides actionable prioritization hints, unlike scattered manual review notes.