Agent skill · data analytics · code-yeongyu
tech-debt-audit
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'.
Why this skill is useful
Adds a comprehensive technical debt audit process with executable commands and structured output that enhances code quality assessment capabilities.
What it needs
Requires codegraph, tree-sitter installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 67,387 stars on the source repository.
What this skill does
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, lspdiagnostics, task). Produces a grounded, citable TECHDEBTAUDIT.md artifact. Output Write results to TECHDEBTAUDIT.md in the repo root with: 1. Executive Summary — 3-5 sentences: overall health, worst dimension, quick wins count 2. Mental Model — the repo's architecture in 1 paragraph (what it does, stack, module boundaries) 3. Findings Table — columns: ID, Category, File:Line, Severity (Critical/High/Medium/Low), Effort (Hours), Description, Recommendation 4. Top 5 Priorities — ranked by impact/effort ratio 5. Quick Wins Checklist — items under 30 minutes each 6. "Looks Bad But Is Fine" — patterns that look like debt but are intentional 7. Open Questions — things the maintainer should clarify Phase 0: Orient Standard (always run) 1. glob("/.ts") / glob("/.py") / etc — map the language stack 2. glob("/package.json") + read() — dependencies and build tooling 3. bash("git log --oneline -200") — churn: find highest-change files 4. glob("/") + basic math — find largest files (>300 LOC are candidates) 5. Cross-reference high-churn + large = debt hot zones 6. 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills code-yeongyu/tech-debt-audit