skills.rest
imgamer
imgamerCOMMUNITY
Explore all skills by this author →
GitHub

tech-debt

Scan codebases for TODO, FIXME, HACK, duplication, and complexity hotspots.

Updated Dec 22, 2024
Search Tags:#code quality#documentation#technical debt#prioritization#sprint planning#code scanning
One-click install
npx skills add https://github.com/imgamer/AILearn --skill tech-debt-imgamer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/imgamer/AILearn/tree/main/game-studios/Claude-Code-Game-Studios-e375f/.claude/skills/tech-debt
Command: npx skills add https://github.com/imgamer/AILearn --skill tech-debt-imgamer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams identify, organize, and schedule technical debt so that growing maintenance risk doesn’t turn into recurring delivery delays and unstable releases.

Core Features & Use Cases

  • Codebase scanning for debt indicators: Finds likely tech debt signals such as TODO/FIXME/HACK markers, deprecated usages, duplication, and potential complexity hotspots by file/function length.
  • Debt register management: Adds new entries with clear categorization and estimated effort, then maintains a consistent register format for visibility and tracking.
  • Prioritization and sprint recommendations: Re-sorts items using a priority score based on impact, frequency of encounter, and fix effort to guide what to tackle next.
  • Read-only reporting: Produces summary statistics (by category, effort totals, and trend direction) and flags items older than 3 sprints for escalation.

Quick Start

Run /tech-debt scan to scan your codebase for tech debt indicators and generate prioritized findings.

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 indicators like TODO and FIXME markers in my codebase?▼

Scanning a codebase for TODO, FIXME, HACK, deprecated markers, duplication, and complexity hotspots identifies technical debt indicators and generates a prioritized register to track maintenance risk.

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

Technical debt prioritization for sprint planning re-sorts items using a priority score based on impact, frequency of encounter, and fix effort to guide what to tackle next.

Can I generate summary statistics and trend reports for my technical debt register?▼

Yes, you can generate read-only technical debt reports that produce summary statistics by category, effort totals, trend direction, and flag items older than 3 sprints for escalation.

Does this technical debt scanning approach work without external code quality dependencies?▼

Yes, this technical debt scanning approach operates with no external dependencies, using subcommand-driven execution to scan codebases and write findings directly to a markdown register.

How do I add new technical debt items with category and effort estimates?▼

You can add new technical debt items to the register by specifying a clear categorization and estimated fix effort, maintaining a consistent format for visibility and tracking.

Related Skills

Explore More Software Engineering Skills→
nikhillinitnikhillinit

tech-debt-tracker

Detect and prioritize technical debt with configurable thresholds and SQALE metrics.

Community
Advanced
brand6brand6

tech-debt

Scan codebases to identify technical debt and update a prioritized debt register.

Community
Intermediate
HomericIntelligenceHomericIntelligence
18

detect-code-smells

Detect code smells and complexity issues in codebases.

Official
Intermediate
xlelibertyxleliberty

code-reviewer

Analyze git pull requests for security vulnerabilities and SOLID violations.

Community
Advanced