skills.rest
sumilee-pcu
sumilee-pcuCOMMUNITY
Explore all skills by this author →
GitHub

tech-debt

Scan source code for TODOs and complexity hotspots to manage technical debt.

Updated Apr 15, 2026
Search Tags:#code quality#refactoring#maintenance#technical debt#sprint planning
One-click install
npx skills add https://github.com/sumilee-pcu/game2026 --skill tech-debt-sumilee-pcu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/sumilee-pcu/game2026/tree/main/.claude/skills/tech-debt
Command: npx skills add https://github.com/sumilee-pcu/game2026 --skill tech-debt-sumilee-pcu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the accumulation of unmanaged technical debt by providing a structured framework to identify, categorize, and prioritize code quality issues before they impact project velocity.

Core Features & Use Cases

  • Automated Debt Scanning: Automatically identifies TODOs, FIXMEs, HACKs, and code complexity hotspots across the repository.
  • Prioritization Engine: Uses a scoring algorithm based on impact and effort to recommend which debt items should be addressed in the next sprint.
  • Use Case: Use this tool at the start of a new sprint to generate a report of all accumulated technical debt and automatically update the project's debt register to ensure the team focuses on the most critical architectural improvements.

Quick Start

Use the tech-debt skill to scan the entire codebase for debt indicators and generate a summary report.

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 categorize technical debt across my codebase?▼

You can prioritize refactoring tasks by using the built-in scoring algorithm, which evaluates technical debt items based on their impact and effort to recommend what to address during sprint planning.

What is the best way to prioritize refactoring tasks for an upcoming sprint?▼

You can prioritize refactoring tasks by using the built-in scoring algorithm, which evaluates technical debt items based on their impact and effort to recommend what to address during sprint planning.

How does automated debt scanning identify code complexity hotspots?▼

Automated debt scanning identifies code complexity hotspots by systematically parsing your source code to detect predefined markers such as TODOs, FIXMEs, and HACKs accumulated across the repository.

Can I generate actionable reports to track debt trends over time?▼

Yes, you can generate actionable reports that track debt trends over time, providing a structured framework to monitor accumulated technical debt and ensure critical architectural improvements are addressed.

When should I scan my repository for technical debt indicators?▼

You should scan your repository for technical debt indicators at the start of a new sprint to generate a summary report, automatically update the debt register, and maintain project velocity.

Related Skills

Explore More Software Engineering Skills→
tranhieutttranhieutt
70

tech-debt

Scan codebase markers and update the technical debt register.

Community
Advanced
cegit27cegit27
3

retro

Analyze git commit history to generate weekly retrospective reports.

Official
Advanced
MathiasPaulenkoMathiasPaulenko

sonarqube-quality-gates

Enforce SonarQube quality gates and static analysis in CI/CD pipelines.

Community
Advanced
luispabonluispabon
6

slop-detector

Crawl codebase directories to identify technical debt and code smells.

Community
Advanced