skills.rest
epicsagas
epicsagasCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

tech-debt-scan

Scan codebases for TODO, FIXME, HACK, and XXX markers and score them by severity, age, and blast radius.

1|Updated May 14, 2026
Search Tags:#static-analysis#risk-management#code-review#tech-debt#remediation-planning
One-click install
npx skills add https://github.com/epicsagas/epicsagas --skill tech-debt-scan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt-scan
Source: https://github.com/epicsagas/epicsagas/tree/main/skills/tech-debt-scan
Command: npx skills add https://github.com/epicsagas/epicsagas --skill tech-debt-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tech Debt Scan identifies, quantifies, and prioritizes technical debt markers (TODO, FIXME, HACK, XXX) across a codebase, turning hidden risk into actionable remediation.

Core Features & Use Cases

  • Debt discovery: scans code to surface TODO, FIXME, HACK, XXX, and other debt markers.
  • Risk scoring: assigns severity, age, and blast radius to each debt item.
  • Remediation planning: generates a prioritized plan with concrete steps.

Quick Start

Scan the repository to generate a prioritized debt remediation plan.

Frequently Asked Questions about tech-debt-scan

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

FAQPage Schema
How do I identify and prioritize technical debt markers across a codebase?▼

To identify technical debt, scan your codebase for TODO, FIXME, HACK, and XXX markers. The scan scores each item by severity, age, and blast radius to produce a prioritized remediation plan for engineering teams.

What is the best way to quantify code debt risk for remediation planning?▼

The best way to quantify code debt risk is to score each marker by its severity, age, and blast radius. This scoring method transforms hidden risk into an actionable, prioritized remediation plan.

How does static analysis calculate the blast radius of technical debt?▼

Static analysis calculates the blast radius of technical debt by inventorying debt markers and evaluating their potential impact across the codebase. This assessment contributes to the overall risk score for prioritized remediation.

Can I generate an actionable report for technical debt remediation planning?▼

Yes, you can generate an actionable report for technical debt remediation. The scan summarizes discovered debt markers and their risk scores into a concrete report suitable for engineering teams to plan fixes.

Does technical debt scanning work with existing code review and risk management workflows?▼

Technical debt scanning integrates with risk management and code review workflows by producing a prioritized inventory of debt markers. This output provides concrete risk scores and remediation steps directly usable by engineering teams.

Related Skills

Explore More Software Engineering Skills→
wfukatsuwfukatsu
5

system-investigation

Analyze codebase tech stack, module layout, and debt hotspots for refactoring.

Community
Advanced
babuallybabually
1

to-issues

Break plans, specs, and PRDs into actionable issue tracker tickets.

Community
Advanced
MathiasPaulenkoMathiasPaulenko

sonarqube-quality-gates

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

Community
Advanced
mmsu-pawpatrolmmsu-pawpatrol
2

security-review

Analyze code repositories for injection, deserialization, and misconfiguration vulnerabilities.

Official
Advanced