Agent skill · Security

tech-debt-audit

Thorough, file-cited technical debt audit across 9 dimensions using AST-grep (tree-sitter), grep, language-native tooling, and optionally CodeGraph knowledge graph. 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'.

YeonGyu-Kim69,732★ · +488/wk · 2 repos on radarProfile →
claude-codecodexcursorNOASSERTION
Install
npx skills add code-yeongyu/oh-my-openagent --skill tech-debt-audit --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 13 KB
Bundled scripts: none
Path: .agents/skills/tech-debt-audit/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 67,209 · +483 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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`) plus **optional CodeGraph MCP** for enhanced code graph analysis when available. Produces a grounded, citable `TECH_DEBT_AUDIT.md` artifact. ## CodeGraph Enhancement (Optional) If you have [CodeGraph](https://github.com/colbymchenry/codegraph) installed (check with `codegraph status`), its MCP tools (`codegraph_search`, `codegraph_callers`, `codegraph_callees`, `codegraph_impact`, `codegraph_explore`, etc.) can supersede or augment the standard tool searches in the dimensions marked below. CodeGraph gives you: - **Symbol search** — instant by-name lookup via FTS5 - **Call graph analysis** — callers/callees for any function - **Impact analysis** — blast radius before changing any symbol - **Smart context building** — entry points, related symbols, and snippets in one call - **Framework-aware routes** — URL patterns linked to their handlers To use CodeGraph, ensure the `codegraph` MCP server is configured in your project's `.mcp.json` or global MCP config. The skill will auto-detect CodeGraph by check

What's inside
Steps it walks through
  1. CodeGraph Enhancement (Optional)
  2. Output
  3. Phase 0: Orient
  4. Standard (always run)
  5. CodeGraph Enhancement (if available)
  6. Phase 1: Audit Across 9 Dimensions
  7. 1. Architectural Decay
  8. 2. Consistency Rot
  9. 3. Type & Contract Debt
  10. 4. Test Debt
  11. 5. Dependency & Config Debt
  12. 6. Performance & Resource Hygiene
  13. 7. Error Handling & Observability
  14. 8. Security Hygiene
More from oh-my-openagent
All skills →
About this skill
What does the tech-debt-audit skill do?

Thorough, file-cited technical debt audit across 9 dimensions using AST-grep (tree-sitter), grep, language-native tooling, and optionally CodeGraph knowledge graph. 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'.

How do I install it?

Run `npx skills add code-yeongyu/oh-my-openagent --skill tech-debt-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From code-yeongyu/oh-my-openagent, a repository with 67,209 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going