tech-debt

Scan codebases for debt indicators and generate prioritization schedules.

Updated Feb 8, 2024
One-click install
npx skills add https://github.com/kay6198835/Game-RPG --skill tech-debt-kay6198835
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/kay6198835/Game-RPG/tree/main/.claude/skills/tech-debt
Command: npx skills add https://github.com/kay6198835/Game-RPG --skill tech-debt-kay6198835

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track, categorize, and prioritize technical debt across the codebase to keep systems healthy and maintainable.

Core Features & Use Cases

  • Debt scanning: detect TODO/FIXME/HACK markers, deprecated markers, and large files.
  • Debt register: maintain a living list of debt items with categorization and prioritization.
  • Scheduling: recommend repayment plans and sprint alignment.

Quick Start

Ask the agent to scan the repository for debt indicators and review 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 across my codebase?

You can track technical debt by scanning the codebase for indicators like TODO and FIXME markers, logging items into a debt register, and generating prioritized repayment schedules aligned to sprints.

What is the best way to scan for tech debt indicators like deprecated markers and large files?

Scanning for tech debt involves detecting TODO, FIXME, and HACK markers alongside deprecated markers and large files, then logging these findings into a categorized debt register for maintenance planning.

Does this technical debt tracking approach work for codebases of varying sizes?

Yes, technical debt scanning and prioritization is applicable to codebases of varying sizes, enabling consistent detection of debt indicators and scheduling of repayment plans regardless of repository scale.

How do I generate a repayment plan for technical debt during sprint planning?

Generate a technical debt repayment plan by reviewing the debt register and using the scheduling phase to recommend prioritized debt items aligned with upcoming sprint planning cycles.

What limitations exist when managing a living list of technical debt items?

Managing a living technical debt list relies on deterministic scan, add, prioritize, and report phases, meaning it requires manually adding unscanned debt items and does not automatically refactor code.

Can I categorize code maintenance issues and generate a summary report?

Yes, you can categorize code maintenance issues within the debt register and use the report phase to generate a summary view of tracked technical debt items and their prioritization status.