skills.rest
rakhnianskii9
rakhnianskii9COMMUNITY
Explore all skills by this author →
GitHub

tech-debt

Scan codebases for TODO/FIXME/HACK markers and maintain a prioritized debt register.

Updated Apr 24, 2026
Search Tags:#refactoring#prioritization#backlog#code-quality#code-review#technical-debt
One-click install
npx skills add https://github.com/rakhnianskii9/God-Godot --skill tech-debt-rakhnianskii9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/rakhnianskii9/God-Godot/tree/main/.github/skills/tech-debt
Command: npx skills add https://github.com/rakhnianskii9/God-Godot --skill tech-debt-rakhnianskii9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Technical debt slows development and increases risk. This Skill provides a centralized process to detect debt signals, log items, and prioritize repayments to keep the codebase healthy.

Core Features & Use Cases

  • Scan the codebase for debt indicators (TODO, FIXME, HACK, deprecated APIs) and log findings.
  • Maintain a debt register with priority, effort estimates, and recommended remediation.
  • Generate reports and sprint-ready plans to guide refactoring and debt repayment.

Quick Start

Scan the codebase for debt indicators and add initial entries to 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 technical debt across a multi-module codebase?▼

You can track technical debt across a multi-module codebase by scanning for TODO, FIXME, and HACK markers, then logging findings into a centralized debt register with priority and effort estimates.

How do I prioritize refactoring tasks from code review findings?▼

Prioritize refactoring tasks by maintaining a debt register that tracks impact, priority levels, and effort estimates, which generates sprint-ready plans to guide code review remediation.

Can I scan my codebase for TODO and FIXME markers to log technical debt?▼

Yes, you can scan your codebase for TODO, FIXME, and HACK markers using a debt-scanner workflow that detects these indicators and automatically adds entries to your debt register.

What is the best way to manage technical debt during ongoing feature work?▼

The best way to manage technical debt during ongoing feature work is to continuously scan for debt indicators, log items with impact assessments, and generate review-ready reports for sprint planning.

Does technical debt management work for multi-module codebases with deprecated APIs?▼

Yes, technical debt management applies to multi-module codebases and can detect deprecated APIs alongside TODO and FIXME markers, maintaining a comprehensive debt register for ongoing feature work.

How do I generate sprint-ready plans for technical debt repayment?▼

Generate sprint-ready plans for technical debt repayment by logging debt items with priority and effort estimates in a register, then outputting actionable remediation plans from the tracked entries.

Related Skills

Explore More Software Engineering Skills→
tranhieutttranhieutt
70

tech-debt

Scan codebase markers and update the technical debt register.

Community
Advanced
ConsiliencyConsiliency
8

security-audit

Scan codebases for OWASP vulnerabilities and generate prioritized remediation reports.

Official
Intermediate
amanhsnamanhsn

Tech Debt Tracker

Scan codebases to identify, quantify, and prioritize technical debt.

Community
Advanced
WindXRanWindXRan

tech-debt

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

Community
Intermediate