Tech Debt Audit

This is a Hermes-native tech-debt-audit workflow skill.

Why This Exists

tech-debt-audit exists so accumulated debt becomes a ranked, reconcilable ledger instead of a one-off complaint: findings cite file:line, severity and effort make the trade-off explicit, quick wins are separated from big fixes, and reruns mark what was resolved instead of rediscovering it.

Do Not Use When

• The target is one diff, PR, or claim rather than the codebase's accumulated state; use code-review.
• The user wants the debt removed now, behavior preserved; use ai-slop-cleaner for deletion-first cleanup.
• A boundary-changing fix from the ledger needs its execution shaped into phases; use refactor-plan.
• The question is release risk for a specific deploy rather than source quality; use production-audit.

Examples

Good example: