tech-debt

Scan codebases for debt indicators and generate prioritized debt reports.

Updated May 16, 2026
One-click install
npx skills add https://github.com/SeongHuni/LightNShadowSurviver --skill tech-debt-seonghuni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/SeongHuni/LightNShadowSurviver/tree/main/GameStudio/codex/skills/tech-debt
Command: npx skills add https://github.com/SeongHuni/LightNShadowSurviver --skill tech-debt-seonghuni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a structured approach to tracking, categorizing, and prioritizing technical debt, helping developers maintain code quality and project organization.

Core Features & Use Cases

  • Tech Debt Tracking: Identifies and categorizes technical debt indicators such as TODO, FIXME, HACK comments, and duplicated code.
  • Debt Register Management: Manages a register of technical debt with details like description, affected files, and impact.
  • Prioritization: Scores and prioritizes debt items based on impact and effort, aiding in sprint planning.
  • Reporting: Generates summary reports of debt status and trends.
  • Use Case: A developer can use this Skill to scan their codebase for technical debt, add new debt entries, prioritize them, and generate reports to inform their sprint planning.

Quick Start

Run the tech-debt skill with the 'scan' subcommand to start tracking technical debt in your codebase.

Frequently Asked Questions about tech-debt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track technical debt across my codebase?

To track technical debt across a codebase, you can run a scan to identify indicators like TODO, FIXME, and HACK comments. The scan categorizes these items and maintains a debt register with descriptions, affected files, and impact details.

Can I prioritize technical debt for sprint planning?

Yes, you can prioritize technical debt for sprint planning by scoring debt items based on their impact and effort. This scoring mechanism helps developers determine which issues to address first during continuous integration workflows.

What is the best way to manage a technical debt register?

The best way to manage a technical debt register is to scan your codebase to automatically populate entries, then categorize them by impact and effort. This structured approach maintains code quality and generates status reports to inform project organization.

How does technical debt scanning identify duplicated code?

Technical debt scanning identifies duplicated code alongside TODO, FIXME, and HACK comments by reading project files and executing scripts. These indicators are then compiled into a centralized register for tracking and prioritization.

Can I generate reports on technical debt trends?

Yes, you can generate summary reports on technical debt trends and status. The reporting feature analyzes the maintained debt register to provide insights into codebase health and inform future sprint planning.

Does technical debt tracking work with continuous integration workflows?

Yes, technical debt tracking is explicitly designed for continuous integration and sprint planning workflows. It requires file read and write access, script execution capabilities, and user interaction to collect the necessary information for maintaining the debt register.