New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Omh Tech Debt Audit

by rlaope in rlaope/oh-my-hermes

[omh] Accumulated tech debt to rank: build the severity-by-effort debt ledger from observed repo evidence - orient, audit the named dimensions with file:line citations, rank fixes and quick wins -…

MITAuto-check passedDevelopment

Install Omh Tech Debt Audit

skills CLI
$ npx skills add rlaope/oh-my-hermes --skill omh-tech-debt-audit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install rlaope/oh-my-hermes omh-tech-debt-audit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/omh-tech-debt-audit .claude/skills/omh-tech-debt-audit && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
omh-tech-debt-audit
GitHub stars
3.2k
Token cost
~2.1k tokens
SKILL.md length
1,054 words
Files
2 (incl. references)
Skills in repo
143
Repo updated
First seen
Licence
MIT

At a glance

[omh] Accumulated tech debt to rank: build the severity-by-effort debt ledger from observed repo evidence - orient, audit the named dimensions with file:line citations, rank fixes and quick wins -…

  • The user says: tech-debt-audit
  • SKILL.md covers Why This Exists, Do Not Use When, Examples and Completion Checklist, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tech debt audit

What it does

Omh Tech Debt Audit is an agent skill from rlaope/oh-my-hermes. [omh] Accumulated tech debt to rank: build the severity-by-effort debt ledger from observed repo evidence - orient, audit the named dimensions with file:line citations, rank fixes and quick wins - and reconcile RESOLVED/NEW/CARRIED against the previous ledger on rerun. Use when the user says: tech-debt-audit, tech debt, tech debt audit, technical debt, technical debt audit, tech debt ledger, debt ledger, audit our tech debt.

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/debt-dimensions.md`).

It sits in Development, covering Technical debt. The repository describes itself as: All in one plugin for Hermes Agent ⚚ the coding intelligence, a long-term memory system and model optimized workflow packages. The licence is MIT.

When your agent uses it

  • The user says: tech-debt-audit
  • Tech debt audit
  • Technical debt audit
  • Tech debt ledger

Example prompts

  • “/omh-tech-debt-audit”

What it can do on your machine

Read from SKILL.md and the folder at commit 7cd0d02. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Omh Tech Debt Audit loads about 2.1k tokens when it runs, and up to ~3.1k if it reads all its reference files. Until then it costs about 112 tokens; SKILL.md has 1,054 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~112
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from rlaope/oh-my-hermes at commit 7cd0d02, republished under its MIT licence (© rlaope). 1,054 words, ~2,067 tokens.

Download SKILL.mdSave it as .claude/skills/omh-tech-debt-audit/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
omh-tech-debt-audit
description
[omh] Accumulated tech debt to rank: build the severity-by-effort debt ledger from observed repo evidence - orient, audit the named dimensions with file:line citations, rank fixes and quick wins - and reconcile RESOLVED/NEW/CARRIED against the previous ledger on rerun. Use when the user says: tech-debt-audit, tech debt, tech debt audit, technical debt, technical debt audit, tech debt ledger, debt ledger, audit our tech debt.

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:

  • Prompt: Audit our tech debt and tell me what to fix first - we have maybe two weeks of cleanup budget.
  • Expected behavior: Orientation from manifests and churn, dimension-by-dimension findings with file:line citations, the severity-by-effort ledger with top fixes and quick wins sized to the budget, and the looks-bad-but-fine list.
  • Why: A budgeted what-to-fix-first question is exactly the ranked ledger this workflow produces.

Bad example:

  • Prompt: This module is a mess, rewrite it properly.
  • Expected behavior: Refuse the rewrite framing: audit the module into ledger findings with bounded fixes, or route a decided restructure to refactor-plan.
  • Why: A rewrite recommendation is the failure mode the ledger exists to replace with bounded, ranked fixes.

Completion Checklist

  • Orientation evidence is observed: manifests, churn ranking, and largest files are named, not assumed.
  • Every finding has id, dimension, file:line, severity, effort, and a bounded recommendation.
  • Quick wins and top fixes are ranked, and the looks-bad-but-is-actually-fine section is present.
  • On rerun, every prior finding is reconciled RESOLVED, CARRIED, or superseded - none silently dropped.

Recovery Notes

  • If the stack is unrecognized, orient from the manifests first and say which dimensions lack detection commands rather than guessing.
  • If a finding cannot be cited to file:line, demote it to an open question and keep it out of the ranked table.
  • If the previous ledger's ids no longer match the tree, map them by dimension plus path before declaring anything RESOLVED.

Workflow Lane

  • Current lane: Coding handoff (idea-to-deploy, llm-app-dev, cto-loop, deploy-and-monitor, code-review, build-failure-triage, verification-gate, security-safety-review, +28 more) - coding owners, handoffs, review, CI, and merge evidence.
  • If intent belongs to another lane, hand back to oh-my-hermes or name the adjacent workflow.
  • Shared product, routing, compatibility, and evidence rules: omh-routing/references/skill-common-rail.md.

Use When

Use when the codebase's accumulated debt should be measured and ranked as a ledger - findings with file:line, severity, and effort, quick wins separated from big fixes - rather than judged as a diff or cleaned up on the spot.

Strong routing signals: `tech-debt-audit`, `tech debt`, `tech debt audit`, `technical debt`, `technical debt audit`, `tech debt ledger`, `debt ledger`, `audit our tech debt`, `tech debt report`, `code debt audit`, `where is our tech debt`, `기술부채`, `기술 부채`, `기술부채 감사`, `기술부채 감사해줘`, `기술부채 점검`, `기술부채 장부`, `부채 원장`

Catalog Metadata

Category: maintenance Phase: tech-debt-audit Hermes role: reviewer Quality tier: finding-evidence-gated Reasoning demand: heavy

Quality bar:

  • Orient before auditing: read the manifests, rank churn from the git log, and name the largest and most-changed files - observed evidence, never memory of the tree.
  • Audit dimension by dimension from the named list - architectural decay, consistency rot, type and contract gaps, test debt, dependency and configuration debt, performance and resource debt, error-handling and observability debt, security hygiene, documentation drift; the full contract is omh-tech-debt-audit/references/debt-dimensions.md.
  • Every finding row carries a stable id, its dimension, a file:line citation, a severity, an effort class (S/M/L), and a bounded recommendation - never a rewrite.
  • Close with the mandatory looks-bad-but-is-actually-fine section: deliberate patterns that pattern-match to debt stay off the ledger, with the reason recorded.
  • On rerun, reconcile against the previous ledger before writing a new one: every prior finding is marked RESOLVED with the evidence gone, CARRIED with its age, or superseded by a NEW finding - a rerun that restarts from zero loses the ledger's point.
Show full SKILL.md (399 more words)Show less

Handoff policy:

Hermes owns the orientation, the dimension audit, and the ledger; detection commands run through the operator's terminal and stay prepared_not_observed until their output is seen, and every fix the ledger recommends is coding work for the selected executor lane, never part of the audit.

Required inputs:

  • the repo root or the scoped path list the audit is confined to
  • the stack truth from manifests (package/build files), not from memory of the tree
  • the previous ledger when one exists, so the rerun can reconcile instead of restart

Expected outputs:

  • orientation summary: manifests read, churn ranking, largest files, test and CI entry points
  • findings table per tech_debt_ledger/v1: id, category, file:line, severity, effort, recommendation
  • top fixes ranked by severity and the quick wins ranked by payoff-per-effort
  • the looks-bad-but-is-actually-fine list, and the RESOLVED/NEW/CARRIED reconciliation on rerun

Artifact expectations:

  • debt ledger per omh-tech-debt-audit/references/debt-dimensions.md
  • prepared detection commands named per stack, marked observed only after their output is seen

Safety rules:

  • Never recommend a rewrite; the ledger names bounded fixes or it names nothing.
  • A finding without a file:line citation is an open question, not a finding.
  • Detection commands are prepared context until their exit status and output are observed.
  • A scoped path list is a boundary: out-of-scope findings are reported as out of scope, never audited silently.

Runtime Evidence

Record observed delegation results; otherwise return not_available or not_observed. Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.

  • Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes. Preserve workflow intent and stop conditions; verify before claiming completion. Reply in the user's own words and the host's own voice: its SOUL.md persona owns reply language, tone, speech level, and sentence endings, progress updates included (where it sets no language, use the one the user wrote in), and OMH shapes structure and content only; OMH's record terms (surface, lane, wrapper, handoff, evidence boundary, not_observed) stay in records and tool calls, never in the sentence the user reads unless they ask about one; and when a stop condition or a decision the user owns ends the turn, offer the next action as a question rather than declaring what will not be done.

Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.

Shared product, compatibility, topology, memory, harness, and execution rules: omh-routing/references/skill-common-rail.md. Load it when applicable; otherwise name an unavailable capability.

© rlaope, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/omh-tech-debt-audit of rlaope/oh-my-hermes.

  • SKILL.md
  • references/debt-dimensions.md

Open the folder on GitHubat commit 7cd0d02

Compare with similar skills

Omh Tech Debt Audit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Omh Tech Debt Audit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Omh Tech Debt Audit this skillrlaope/oh-my-hermes3.2k—~2.1kAutomated safety check: PassMIT
Systematic Code Refactoringluongnv89/claude-howto42k—~3kAutomated safety check: PassMIT
Code Simplification for ego-litecitrolabs/ego-lite17k—~1.2kAutomated safety check: PassMIT
Code Refactoring Workflowluongnv89/claude-howto42k—~3.1kAutomated safety check: PassMIT
Cto AdvisorIbrahim-3d/orchestrator-supaconductor3814 repos~2.4kAutomated safety check: PassMIT
Ponytail Debt LedgerDietrichGebert/ponytail160k—~453Automated safety check: PassMIT

Similar skills

  • Systematic Code Refactoring

    luongnv89/claude-howto

    Guides refactoring in phases based on Martin Fowler's method: research, test coverage check, planning and small tested steps, with your approval at each phase.

    42k GitHub stars~3k tokensUpdated today
    DevelopmentAuto-check passed

  • Code Simplification for ego-lite

    citrolabs/ego-lite

    Finds and implements evidence-backed simplifications in the ego-lite repository, such as dead code, duplicated state and speculative abstractions, without hiding behavior changes.

    17k GitHub stars~1.2k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Code Refactoring Workflow

    luongnv89/claude-howto

    Guides systematic, test-backed refactoring in the style of Martin Fowler, moving through research, planning and small incremental changes with your approval at each phase.

    42k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Cto Advisor

    Ibrahim-3d/orchestrator-supaconductor

    Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.

    381 GitHub starsUsed in 4 repos~2.4k tokens
    DevelopmentAuto-check passed

  • Ponytail Debt Ledger

    DietrichGebert/ponytail

    Collects every ponytail: comment in a codebase into one debt ledger, flags shortcuts with no upgrade trigger and reports without changing any files.

    160k GitHub stars~453 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • FIXME Resolver

    tailcallhq/forgecode

    Finds every FIXME comment in a codebase, groups related ones across files into one task, implements the work they describe and removes the comments once it is done.

    7.6k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed

More from rlaope/oh-my-hermes

All 143 skills in this repo

  • Omh Accessibility Audit

    rlaope/oh-my-hermes

    [omh] Screen-reader or keyboard accessibility gaps: prepare WCAG, keyboard, focus, screen-reader, target-size, and reflow evidence gates for UI surfaces.

    3.3k GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • Omh Agent Debug

    rlaope/oh-my-hermes

    [omh] Agent is stuck, looping, or drifting: capture a stuck, looping, drifting, or repeatedly failing agent run, diagnose the likely failure pattern, and prepare the smallest safe recovery action.

    3.3k GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Omh Agent Evaluation

    rlaope/oh-my-hermes

    [omh] Choosing between coding agents on evidence: compare executor or agent choices on reproducible tasks using quality, cost, time, tool, and evidence metrics.

    3.3k GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Omh Agent Instructions

    rlaope/oh-my-hermes

    [omh] Agent instruction file for a repo -- AGENTS.md, CLAUDE.md, a Cursor rule: write or update what an agent cannot derive from the code, inside a marked region, with every command verified or…

    3.3k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Omh Agent Ops Review

    rlaope/oh-my-hermes

    [omh] AI agent progress for managers: help managers inspect AI-agent progress, blockers, quality gates, and throughput levers.

    3.3k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Omh AI Slop Cleaner

    rlaope/oh-my-hermes

    [omh] Messy or AI-generated code to clean up: delete AI-generated slop, dead code, and duplication while observable behavior stays identical.

    3.3k GitHub stars~2.7k tokensUpdated today
    Auto-check passed

Categories

Questions about Omh Tech Debt Audit

What does Omh Tech Debt Audit do?

[omh] Accumulated tech debt to rank: build the severity-by-effort debt ledger from observed repo evidence - orient, audit the named dimensions with file:line citations, rank fixes and quick wins -…. Omh Tech Debt Audit is an agent skill from rlaope/oh-my-hermes. [omh] Accumulated tech debt to rank: build the severity-by-effort debt ledger from observed repo evidence - orient, audit the named dimensions with file:line citations, rank fixes and quick wins - and reconcile RESOLVED/NEW/CARRIED against the previous ledger on rerun.

When should I use Omh Tech Debt Audit?

Omh Tech Debt Audit fits situations like: the user says: tech-debt-audit; tech debt audit; technical debt audit; tech debt ledger.

How do I install Omh Tech Debt Audit in Claude Code?

Run `npx skills add rlaope/oh-my-hermes --skill omh-tech-debt-audit -a claude-code`. Or copy the skill folder (skills/omh-tech-debt-audit in rlaope/oh-my-hermes) into .claude/skills/omh-tech-debt-audit in your project. Claude Code loads it when a task matches its description.

How do I install Omh Tech Debt Audit in Codex?

Run `npx skills add rlaope/oh-my-hermes --skill omh-tech-debt-audit -a codex`. Or copy the skill folder (skills/omh-tech-debt-audit in rlaope/oh-my-hermes) into .agents/skills/omh-tech-debt-audit in your project. Codex loads it when a task matches its description.

Can I use Omh Tech Debt Audit in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rlaope/oh-my-hermes --skill omh-tech-debt-audit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/omh-tech-debt-audit, .gemini/skills/omh-tech-debt-audit, .github/skills/omh-tech-debt-audit and .opencode/skills/omh-tech-debt-audit in your project.

What does Omh Tech Debt Audit need to run?

SKILL.md names no scripts, command-line tools or credentials: Omh Tech Debt Audit is instructions for the agent only.

Does Omh Tech Debt Audit access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Omh Tech Debt Audit safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Omh Tech Debt Audit use?

Omh Tech Debt Audit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Omh Tech Debt Audit use?

About 2.1k tokens (SKILL.md is roughly 8.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1k tokens, read only when the agent opens those files.

What are the alternatives to Omh Tech Debt Audit?

Skills that share tags, products or a category with Omh Tech Debt Audit: Systematic Code Refactoring (luongnv89/claude-howto, 42k stars), Code Simplification for ego-lite (citrolabs/ego-lite, 17k stars), Code Refactoring Workflow (luongnv89/claude-howto, 42k stars) and Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 381 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Omh Tech Debt Audit?

rlaope (a GitHub user) maintains it in rlaope/oh-my-hermes, which has 3,243 GitHub stars. The repository holds 143 skills in this directory. The repository was last updated on October 10, 2026.

Source: rlaope/oh-my-hermes on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.