skills.rest
jtvaris
jtvarisCOMMUNITY
Explore all skills by this author →
GitHub

tech-debt

Scan codebases for TODO/FIXME indicators and update a debt register.

Updated Mar 15, 2026
Search Tags:#codebase#prioritization#code-quality#scanning#sprint-planning#technical-debt#debt-register
One-click install
npx skills add https://github.com/jtvaris/sunday-night-dynasty --skill tech-debt-jtvaris
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/jtvaris/sunday-night-dynasty/tree/main/.agents/skills/tech-debt
Command: npx skills add https://github.com/jtvaris/sunday-night-dynasty --skill tech-debt-jtvaris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track, categorize, and prioritize technical debt across the codebase to improve long-term maintainability and reliability.

Core Features & Use Cases

  • Scan the codebase for debt indicators such as TODO, FIXME, HACK, and deprecated markers; surface duplicates and long files or functions for refactoring.
  • Maintain a debt register and generate prioritization recommendations for sprints and planning.
  • Add debt entries manually with context and impact to ensure traceability and accountability.

Quick Start

Invoke the scan subcommand to detect debt indicators and update the debt register accordingly.

Frequently Asked Questions about tech-debt

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

FAQPage Schema
How do I scan my codebase for technical debt?▼

To scan for technical debt, invoke the scan subcommand to detect indicators like TODO, FIXME, and HACK markers. It automatically surfaces duplicates and long files or functions for refactoring, updating your centralized debt register.

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

Prioritize technical debt by maintaining a centralized debt register with structured entries. Use the prioritize subcommand to generate recommendations for sprint planning based on category, effort, impact, and priority.

Can I manually add technical debt entries with specific context and impact?▼

Yes, you can manually add technical debt entries using the add subcommand. This enforces structured fields including category, description, files, effort, impact, and priority to ensure traceability and accountability.

How does the debt register handle aging technical debt items?▼

The debt register provides ongoing guardrails for aging technical debt items. It tracks lifecycle stages and applies structured entries to ensure old debt remains visible and accountable during reprioritization.

What technical debt indicators can be detected during a codebase scan?▼

Codebase scans detect technical debt indicators such as TODO, FIXME, HACK, and deprecated markers. The scan also identifies duplicate code and long files or functions that require refactoring.

Does tracking technical debt require any external dependencies or components?▼

No, tracking technical debt requires no external dependencies or components. The skill operates independently to scan repositories, catalog debt, and generate reports using built-in subcommands.

Related Skills

Explore More Software Engineering Skills→
brand6brand6

tech-debt

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

Community
Intermediate
ConsiliencyConsiliency
8

security-audit

Scan codebases for OWASP vulnerabilities and generate prioritized remediation reports.

Official
Intermediate
WindXRanWindXRan

tech-debt

Scan codebase indicators, maintain a debt register, and generate sprint-ready reports.

Community
Intermediate
travisjneumantravisjneuman
88

tech-debt-analyzer

Analyze codebases for technical debt using Python static analysis scripts.

Community
Intermediate