skills.rest
dvy1987
dvy1987COMMUNITY
Explore all skills by this author →
WebsiteGitHub

technical-debt-audit

Scan codebases for debt indicators and generate a prioritized remediation roadmap.

3|Updated Apr 5, 2026
Search Tags:#refactoring#audit#reporting#velocity#quadrant#technical-debt#code-health
One-click install
npx skills add https://github.com/dvy1987/agent-loom --skill technical-debt-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: technical-debt-audit
Source: https://github.com/dvy1987/agent-loom/tree/main/.agents/skills/technical-debt-audit
Command: npx skills add https://github.com/dvy1987/agent-loom --skill technical-debt-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit the project's technical health and identify high-interest debt, enabling teams to prioritize fixes and accelerate delivery.

Core Features & Use Cases

  • Scan code for TODO, FIXME, HACK and other debt indicators to surface actionable items.
  • Categorize debt using the Technical Debt Quadrant and assign impact levels to prioritize changes.
  • Produce an audit report with health score, top-priority items, and a remediation roadmap for sprint planning.
  • Save reports to docs/reports and update skill-outputs for traceability.

Quick Start

Run the technical-debt-audit skill on your repository to generate a prioritized refactoring roadmap.

Frequently Asked Questions about technical-debt-audit

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

FAQPage Schema
How do I identify and prioritize high-interest technical debt in my codebase?▼

Prioritize technical debt by scanning for indicators like TODO and FIXME, then categorizing them using the Technical Debt Quadrant. The audit assigns blast-radius scores to each item, producing a prioritized remediation roadmap for sprint planning.

What is the Technical Debt Quadrant and how does it categorize code health?▼

The Technical Debt Quadrant is a framework that categorizes code health issues based on their intent and impact. It distinguishes between reckless and prudent debt, helping teams assign impact levels to prioritize changes and accelerate delivery effectively.

How do I generate a technical debt audit report for sprint planning?▼

Run an audit scan on your repository to generate a technical debt report. It produces an executive summary with a health score, top-priority items, and a QA-ready remediation roadmap, saving the results to docs/reports for sprint planning.

Does a technical debt audit work with repositories of varying sizes and languages?▼

Yes, a technical debt audit applies to repositories of varying sizes and languages. It scans for debt indicators across different codebases, calculating blast-radius scoring and generating an executive summary regardless of the project's scale or programming language.

How do I calculate blast-radius scoring for refactoring tasks?▼

Calculate blast-radius scoring by auditing debt indicators within the codebase to evaluate their potential impact. The audit assigns impact levels to these items, measuring the scope of risk to produce a prioritized refactoring roadmap.

Related Skills

Explore More Software Engineering Skills→
tranhieutttranhieutt
70

tech-debt

Scan codebase markers and update the technical debt register.

Community
Advanced
olaservoolaservo
10

comprehensive-issue-analyzer

Fetch all open GitHub issues via pagination and generate a triage report.

Community
Intermediate
swannysecswannysec
2

impact-flow

Analyze Python and TypeScript codebases to map dependencies, blast radius, health, and execution flow.

Community
Advanced
poz110poz110
4

hotfix

Analyze, code, and verify fixes for urgent software bugs.

Community
Advanced