Tech Debt Audit
Thorough, file-cited technical debt audit across 9 dimensions using AST-grep...
Install
npx skills add code-yeongyu/oh-my-openagent --skill tech-debt-audit -g -a claude-code -y- Repository
- code-yeongyu/oh-my-openagent70.6k
- Category
- Engineering
- Updated
- 3d ago
- License
- See repository
- Context cost
- Mediumabout 2,236 tokens
- Runs scripts
- No, instructions only
What it does
Thorough, file-cited technical debt audit across 9 dimensions using AST-grep (tree-sitter), grep, LSP, and language-native tooling. Produces TECH_DEBT_AUDIT.md with severity, effort estimates, and prioritized fixes. Use when asked for codebase health check, tech debt audit, architecture review, code quality assessment, or cleanup planning. Triggers: 'tech debt', 'technical debt', 'debt audit', 'code health', 'technical debt audit', 'codebase health check', 'find tech debt', 'debt analysis', 'audit code quality'.
Tech Debt Audit Protocol
Model-agnostic technical debt audit for oh-my-openagent (OMO). Uses OMO's built-in tools (grep, glob, bash with sg, read, lsp_diagnostics, task). Produces a grounded, citable TECH_DEBT_AUDIT.md artifact.
Output
Write results to TECH_DEBT_AUDIT.md in the repo root with:
- Executive Summary, 3-5 sentences: overall health, worst dimension, quick wins count
- Mental Model, the repo's architecture in 1 paragraph (what it does, stack, module boundaries)
- Findings Table, columns: ID, Category, File:Line, Severity (Critical/High/Medium/Low), Effort (Hours), Description, Recommendation
- Top 5 Priorities, ranked by impact/effort ratio
- Quick Wins Checklist, items under 30 minutes each
- "Looks Bad But Is Fine", patterns that look like debt but are intentional
- Open Questions, things the maintainer should clarify
Phase 0: Orient
Standard (always run)
glob("**/*.ts")/glob("**/*.py")/ etc, map the language stackglob("**/package.json")+read(), dependencies and build toolingbash("git log --oneline -200"), churn: find highest-change filesglob("**/*")+ basic math, find largest files (>300 LOC are candidates)- Cross-reference high-churn + large = debt hot zones
- Write the mental model paragraph in your own working context
Phase 1: Audit Across 9 Dimensions
Use OMO tools for each dimension. Run parallel tool calls within each dimension. Every finding MUST cite file:line:col.
1. Architectural Decay
Standard (always run)
bash("sg -p \"import { $$$ } from '$SRC'\" -l ts ."), map module graph, look for circular patternsbash("sg -p \"class $NAME { $$$ }\" -l ts ."), check for god classesgrep("TODO|FIXME|HACK|XXX|WORKAROUND|TEMP"), tagged debt markersgrep("async|await")on sync-looking files, misplaced async boundariesbash("wc -l <file>")on each large file found in Phase 0
