tech-debt-audit

Full codebase tech debt audit with 11 parallel agents — finds dependency issues, code smells, architecture problems, test gaps, error handling flaws, performance bottlenecks, security vulnerabilities, documentation gaps, type safety issues, API inconsistencies, and over-engineering

Audits codebase for API design issues: inconsistent endpoint naming, missing pagination, versioning gaps, inconsistent error responses, and missing validation schemas. Spawned by tech-debt-audit command.

Audits codebase for structural issues: circular dependencies, layer violations, pattern inconsistencies, legacy patterns, tight coupling, and missing abstractions. Spawned by tech-debt-audit command.

Audits codebase for code smells: long functions, high complexity, deep nesting, duplication, dead code, magic values, inconsistent naming, and god files. Spawned by tech-debt-audit command.

Audits codebase for over-engineering: unnecessary abstractions, premature generalization, wrapper classes adding no value, indirection layers with single implementations, and enterprise patterns in simple contexts. Spawned by tech-debt-audit command.

Audits codebase for dependency health issues: outdated packages, known CVEs, unused dependencies, unmaintained packages, duplicate versions, and license risks. Spawned by tech-debt-audit command.

Full codebase technical debt audit using 11 parallel specialized agents. Identifies dependency issues, code smells, architecture problems, test gaps, error handling flaws, performance bottlenecks, security vulnerabilities, documentation gaps, type safety issues, API inconsistencies, and over-engineering. Groups findings into actionable GitHub issues. Use when the user asks to audit the codebase, find tech debt, assess code quality, check for technical debt, or run a codebase health check.