skills.rest
CarlosQ96
CarlosQ96COMMUNITY
Explore all skills by this author →
GitHub

tech-debt

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

Updated Apr 9, 2026
Search Tags:#refactoring#code-quality#static-analysis#sprint-planning#tech-debt#risk-prioritization#debt-register
One-click install
npx skills add https://github.com/CarlosQ96/robot-crawler --skill tech-debt-carlosq96
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/CarlosQ96/robot-crawler/tree/main/.agents/skills/tech-debt
Command: npx skills add https://github.com/CarlosQ96/robot-crawler --skill tech-debt-carlosq96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling.

Core Features & Use Cases

  • Scan codebase for debt indicators (TODO, FIXME, HACK, @deprecated) and log findings into a debt register.
  • Classify findings into Architecture Debt, Code Quality Debt, Test Debt, Documentation Debt, Dependency Debt, and Performance Debt.
  • Generate prioritized recommendations and prepare sprint-ready tasks for repayment scheduling.

Quick Start

Run the tech-debt workflow to identify and register debt across the repository.

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?▼

To track and prioritize technical debt, you need to scan your repository for indicators like TODO and FIXME tags, classify them into categories such as architecture or test debt, and generate a prioritized risk register for sprint planning.

What are the main categories of technical debt I should look for during static analysis?▼

The main categories of technical debt to analyze are architecture debt, code quality debt, test debt, documentation debt, dependency debt, and performance debt, which together form a comprehensive risk register.

How do I prepare sprint-ready tasks for repaying technical debt?▼

You prepare sprint-ready tasks for repaying technical debt by categorizing codebase findings into a structured debt register with clear rationale, enabling prioritized scheduling and actionable development workflows.

Can I scan for TODO and FIXME comments to build a debt register?▼

Yes, you can scan for TODO, FIXME, HACK, and deprecated tags to log code quality debt findings directly into a structured debt register, providing clear rationale for each identified item.

What is the best way to categorize dependency and documentation debt for risk prioritization?▼

The best way to categorize dependency and documentation debt is to analyze codebase indicators, classify them into distinct debt types, and produce a prioritized risk register ensuring governance and sprint planning readiness.

Related Skills

Explore More Software Engineering Skills→
hGriff0nhGriff0n

GSD Codebase Mapper

Analyze codebase structure, dependencies, and technical debt to produce ARCHITECTURE.md and STACK.md.

Community
Advanced
LeKayLeKay

tech-debt

Scan codebases for technical debt indicators and maintain a debt register.

Community
Advanced
TraftGTraftG
33

tech-debt

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

Community
Advanced
DonchitosDonchitos
23.7k

tech-debt

Scan codebases for technical debt indicators and maintain a categorized debt register.

Community
Intermediate