tech-debt-audit

Audit codebase technical debt across nine dimensions and generate a prioritized remediation report.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/hsch14/ABC-car_insurance --skill tech-debt-audit-hsch14
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-debt-audit
Source: https://github.com/hsch14/ABC-car_insurance/tree/main/.agents/skills/tech-debt-audit
Command: npx skills add https://github.com/hsch14/ABC-car_insurance --skill tech-debt-audit-hsch14

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill identifies, quantifies, and prioritizes technical debt across nine critical dimensions, transforming vague code quality concerns into actionable remediation plans.

Core Features & Use Cases

  • Multi-Dimensional Audit: Evaluates architecture, consistency, type safety, testing, and security hygiene using AST-grep and optional CodeGraph integration.
  • Prioritized Reporting: Generates a structured TECH_DEBT_AUDIT.md file with severity ratings, effort estimates, and a clear roadmap for refactoring.
  • Use Case: Use this when onboarding to a new legacy codebase or planning a quarterly cleanup sprint to identify high-churn hot zones and critical architectural decay.

Quick Start

Run the tech-debt-audit skill to perform a full codebase health check and generate a prioritized remediation report.

Frequently Asked Questions about tech-debt-audit

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

FAQPage Schema
How do I perform a technical debt audit on a legacy codebase?

Perform a technical debt audit by running static analysis and AST-grep to evaluate architectural decay and codebase health. This process identifies high-churn hot zones and generates a prioritized remediation report with severity ratings.

What is technical debt analysis and when do I need it?

Technical debt analysis is the process of quantifying code quality issues across dimensions like consistency and security hygiene. You need it when onboarding to a legacy codebase or planning a refactoring sprint to prioritize cleanup targets.

How do I identify refactoring targets and high-churn hot zones in my code?

Identify refactoring targets by analyzing codebase health through AST-grep and optional CodeGraph integration to pinpoint high-churn hot zones. This yields a citable audit report with effort estimates for critical architectural decay remediation.

Can I use static analysis to assess architecture decay and security hygiene?

Yes, you can use static analysis to assess architecture decay and security hygiene across nine critical dimensions. It evaluates type safety, testing, and consistency to transform vague code quality concerns into actionable remediation plans.

Does the codebase health audit require CodeGraph MCP integration?

CodeGraph MCP integration is optional for the codebase health audit. The skill performs comprehensive technical debt analysis using AST-grep and static analysis natively, while CodeGraph enhances the detection of architectural decay and high-churn zones.