tech-debt-audit

Audit a codebase for technical debt and generate a prioritized remediation plan.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/wilsto/claude-code-starter-kit --skill tech-debt-audit-wilsto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt-audit
Source: https://github.com/wilsto/claude-code-starter-kit/tree/main/.claude/skills/tech-debt-audit
Command: npx skills add https://github.com/wilsto/claude-code-starter-kit --skill tech-debt-audit-wilsto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the accumulation of technical debt within a codebase, which can slow down development, increase bug rates, and hinder maintainability. It provides a structured assessment and a prioritized plan for remediation.

Core Features & Use Cases

  • Comprehensive Audit: Analyzes code health, test coverage, documentation, and dependencies.
  • Prioritized Remediation: Generates a scored report with actionable steps for fixing debt.
  • Use Case: A team notices development velocity is decreasing. They use this skill to get a clear picture of where technical debt is most impactful and create a focused refactoring roadmap.

Quick Start

Initiate a full project audit, focusing on code health and dependencies, with a strict severity threshold.

Frequently Asked Questions about tech-debt-audit

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

FAQPage Schema
How do I audit my codebase for technical debt and create a remediation plan?▼

To audit technical debt, analyze your codebase across code health, test reliability, documentation, and dependencies. The audit identifies anti-patterns and scores files to produce a prioritized remediation plan based on your defined scope and severity thresholds.

What is the best way to identify code anti-patterns affecting maintainability?▼

The best way to identify code anti-patterns affecting maintainability is to perform a comprehensive code health audit. This process evaluates code quality dimensions and scores individual files to highlight where technical debt is most impactful.

Can I scope a technical debt audit to specific dimensions and severity thresholds?▼

Yes, you can scope a technical debt audit to specific dimensions such as code health or dependencies. You define the constraints and severity thresholds, and the audit generates a prioritized remediation plan focused on those exact parameters.

When should I run a code health audit to assess technical debt?▼

You should run a code health audit to assess technical debt when development velocity decreases or bug rates increase. The audit provides a structured assessment of your codebase to create a focused refactoring roadmap.

Does this technical debt analysis cover dependencies and infrastructure?▼

Yes, technical debt analysis covers dependencies and infrastructure. The audit evaluates dependencies and infra alongside test reliability and documentation specs to identify anti-patterns and generate a scored remediation report.