New: 97,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

Oma Debug

by first-fluke in first-fluke/oh-my-agent

Bug diagnosis and fixing specialist - analyzes errors, identifies root causes, provides fixes, and writes regression tests.

MITAuto-check passedDevelopment

Install Oma Debug

skills CLI
$ npx skills add first-fluke/oh-my-agent --skill oma-debug -a claude-code

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

GitHub CLI
$ gh skill install first-fluke/oh-my-agent oma-debug --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/first-fluke/oh-my-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/benchmarks/runs/oma/.agents/skills/oma-debug .claude/skills/oma-debug && 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
oma-debug
GitHub stars
1.3k
Token cost
~1.5k tokens
SKILL.md length
672 words
Files
8
Skills in repo
57
Repo updated
First seen
Licence
MIT

At a glance

Bug diagnosis and fixing specialist - analyzes errors, identifies root causes, provides fixes, and writes regression tests.

  • Works in 3 steps: Capture the reported symptom and… → Reproduce or establish the closest… → Identify affected files, tests, and…
  • Regression work
  • SKILL.md covers Scheduling, Structural Flow, Logical Operations and References
  • Calls rg

What it does

Oma Debug is an agent skill from first-fluke/oh-my-agent. Bug diagnosis and fixing specialist - analyzes errors, identifies root causes, provides fixes, and writes regression tests. Use for bug, debug, error, crash, traceback, exception, and regression work.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files (for example `resources/bug-report-template.md`, `resources/checklist.md` and `resources/common-patterns.md`).

It sits in Development, covering Root cause analysis and Debugging. The repository describes itself as: Mechanical verification for AI coding agents — skills pack or full harness (stop-hook gates, artifact checks, independent judges). The licence is MIT.

When your agent uses it

  • Regression work
  • Tasks that involve Root cause analysis
  • Tasks that involve Debugging

Example prompts

  • “/oma-debug”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Capture the reported symptom and suspected scope.
  2. Reproduce or establish the closest reliable failing signal.
  3. Identify affected files, tests, and related patterns.

What it can do on your machine

Read from SKILL.md and the folder at commit 0e87272. 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

    Shell commands in SKILL.md call:

    • rg

    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

Oma Debug loads about 1.5k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 672 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~53
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

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 first-fluke/oh-my-agent at commit 0e87272, republished under its MIT licence (© first-fluke). 672 words, ~1,533 tokens.

Download SKILL.mdSave it as .claude/skills/oma-debug/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
oma-debug
description
Bug diagnosis and fixing specialist - analyzes errors, identifies root causes, provides fixes, and writes regression tests. Use for bug, debug, error, crash, traceback, exception, and regression work.

Debug Agent - Bug Fixing Specialist

Scheduling

Goal

Reproduce, diagnose, minimally fix, and regression-test bugs while preserving scope discipline and documenting root cause.

Intent signature
  • User reports a bug, crash, traceback, exception, error message, performance issue, intermittent failure, or regression.
  • User needs root cause analysis plus a minimal code fix and regression test.
When to use
  • User reports a bug with error messages
  • Something is broken and needs fixing
  • Performance issues or slowdowns
  • Intermittent failures or race conditions
  • Regression bugs
When NOT to use
  • Building new features -> use Frontend/Backend/Mobile agents
  • General code review -> use QA Agent
Expected inputs
  • Error message, failing behavior, reproduction steps, logs, test failure, or affected code path
  • Existing tests, stack traces, environment notes, and suspected regression boundary
Expected outputs
  • Root cause explanation
  • Minimal fix scoped to the failing behavior
  • Regression test or explicit reason it cannot be added
  • Bug documentation under .agents/results/bugs/ when appropriate
Dependencies
  • resources/execution-protocol.md, examples, checklist, common patterns, and debugging checklist
  • Local codebase search and symbol/reference tools
  • Project test, lint, typecheck, and runtime commands
Control-flow features
  • Branches by reproduction success, error class, suspected layer, and verification outcome
  • Reads logs/code/tests and writes code/tests/docs
  • Must search for similar patterns after fixing

Structural Flow

Entry
  1. Capture the reported symptom and suspected scope.
  2. Reproduce or establish the closest reliable failing signal.
  3. Identify affected files, tests, and related patterns.
Scenes
  1. PREPARE: Gather symptoms, logs, reproduction path, and verification command.
  2. ACQUIRE: Read failing code, tests, references, and similar patterns.
  3. REASON: Isolate root cause and reject unsupported hypotheses.
  4. ACT: Apply minimal fix and regression test.
  5. VERIFY: Re-run failing and related checks.
  6. FINALIZE: Document root cause, fix, test, and residual risk.
Transitions
  • If reproduction fails, use logs/tests to establish a weaker but explicit diagnostic signal.
  • If the first fix fails verification, return to root-cause analysis.
  • If similar patterns exist, inspect and patch only affected cases.
  • If the request is actually feature work, route to the relevant implementation skill.
Failure and recovery
  • If environment is missing, document the blocker and provide the closest static diagnosis.
  • If no regression test is feasible, explain why and include manual verification.
  • If fix scope grows, stop and call out the broader design issue.
Exit
  • Success: bug is fixed, regression coverage exists, and checks pass.
  • Partial success: root cause or verification blocker is explicit.

Logical Operations

Show full SKILL.md (286 more words)Show less
Actions
ActionSSL primitiveEvidence
Reproduce failureCALL_TOOLTest/runtime/log command
Search affected codeREADCode, tests, symbols, references
Compare similar patternsCOMPAREPattern search
Infer root causeINFERDiagnostic reasoning
Write minimal fixWRITECode patch
Write regression testWRITETest patch
Verify behaviorVALIDATETests/checks
Report resultNOTIFYRoot-cause summary
Tools and instruments
  • Project test, lint, typecheck, runtime, and logging commands
  • Serena MCP symbol/reference/pattern search when available
  • Debugging checklist and bug report template
Canonical workflow path
bash
rg "<error-message-or-symbol>"
rg --files

Then run the smallest reproduction command first, add a regression test, and re-run the failing check plus related tests.

Resource scope
ScopeResource target
CODEBASEFailing source, tests, and related patterns
LOCAL_FSBug reports and result artifacts
PROCESSReproduction and verification commands
MEMORYHypotheses, root-cause notes, verification evidence
Preconditions
  • A bug signal, symptom, or failing behavior is available.
  • Relevant code and verification path can be inspected or the blocker is stated.
Effects and side effects
  • Mutates source/tests only as needed for the fix.
  • May create bug documentation under .agents/results/bugs/.
Guardrails
  1. Reproduce first, then diagnose - never guess at fixes
  2. Identify root cause, not just symptoms
  3. Minimal fix: change only what's necessary
  4. Every fix gets a regression test
  5. Search for similar patterns elsewhere after fixing
  6. Document in .agents/results/bugs/
Serena MCP
  • find_symbol("functionName"): Locate the function
  • find_referencing_symbols("Component"): Find all usages
  • search_for_pattern("error pattern"): Find similar issues

References

Follow resources/execution-protocol.md step by step. See resources/examples.md for input/output examples. Before submitting, run resources/checklist.md. Vendor-specific execution protocols are injected automatically by oma agent:spawn. Source files live under ../_shared/runtime/execution-protocols/{vendor}.md.

  • Execution steps: resources/execution-protocol.md
  • Code examples: resources/examples.md
  • Checklist: resources/checklist.md
  • Error recovery: resources/error-playbook.md
  • Bug report template: resources/bug-report-template.md
  • Common patterns: resources/common-patterns.md
  • Debugging checklist: resources/debugging-checklist.md
  • Context loading: ../_shared/core/context-loading.md
  • Reasoning templates: ../_shared/core/reasoning-templates.md
  • Context budget: ../_shared/core/context-budget.md
  • Lessons learned: ../_shared/core/lessons-learned.md

© first-fluke, 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 7 other files in benchmarks/runs/oma/.agents/skills/oma-debug of first-fluke/oh-my-agent.

  • SKILL.md
  • resources/bug-report-template.md
  • resources/checklist.md
  • resources/common-patterns.md
  • resources/debugging-checklist.md
  • resources/error-playbook.md
  • resources/examples.md
  • resources/execution-protocol.md

Open the folder on GitHubat commit 0e87272

Compare with similar skills

Oma Debug 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.

Oma Debug compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Oma Debug this skillfirst-fluke/oh-my-agent1.3k—~1.5kAutomated safety check: PassMIT
OpenROAD Bug FixerThe-OpenROAD-Project/OpenROAD3.2k—~784Automated safety check: PassBSD-3-Clause
Triagebot Action Bug Triagewithastro/astro63k—~639Automated safety check: PassCustom licence
Root Cause Debuggingjsmastery-pro/skills1.4k—~1.8kAutomated safety check: NotesMIT
Issue TracerZaxbyHub/opencode-swarm488—~4.4kAutomated safety check: PassMIT
Superpowers Systematic Debuggingchristopherarter/superpowers-reasonix102—~2kAutomated safety check: PassMIT

Similar skills

  • OpenROAD Bug Fixer

    The-OpenROAD-Project/OpenROAD

    Fixes an OpenROAD bug from a GitHub issue or error code: finds the root cause, implements the fix, adds a regression test and prepares a signed-off commit.

    3.2k GitHub stars~784 tokensUpdated today
    DevelopmentAuto-check passed

  • Triagebot Action Bug Triage

    withastro/astro

    Official

    Takes a bug report for the triagebot-action GitHub Action through reproduction, root-cause diagnosis, an intended-behavior check and a fix attempt.

    63k GitHub stars~639 tokensUpdated today
    DevelopmentAuto-check passed

  • Root Cause Debugging

    jsmastery-pro/skills

    Runs a reproduce, localize, hypothesize, test, fix and verify loop to find a bug's root cause, applies the minimal fix and hands off a regression test.

    1.4k GitHub stars~1.8k tokensUpdated 1 mo ago
    DevelopmentAuto-check: notes

  • Issue Tracer

    ZaxbyHub/opencode-swarm

    Drives a bug report from validation and root-cause tracing through a critic-reviewed plan, an approved minimal fix and a PR-ready closure, never merging without recorded human approval.

    488 GitHub stars~4.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Superpowers Systematic Debugging

    christopherarter/superpowers-reasonix

    Any bug, failing or flaky test, or surprise behavior?. An agent skill from christopherarter/superpowers-reasonix.

    102 GitHub stars~2k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Minimal Code Fix

    cobusgreyling/loop-engineering

    Makes the smallest code change that fixes one well-scoped problem, such as a CI failure, review comment or typo, without refactoring anything unrelated.

    11k GitHub starsUsed in 1 repo~345 tokens
    DevelopmentAuto-check: notes

More from first-fluke/oh-my-agent

All 57 skills in this repo

  • OMA Multi-Agent Orchestration

    first-fluke/oh-my-agent

    Decomposes a complex feature into tasks, dispatches parallel specialist agents with durable state, and supervises verification, QA review and retries.

    1.3k GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

  • OMA Multi-Agent Orchestrator

    first-fluke/oh-my-agent

    Splits a complex feature into prioritized tasks, spawns specialist CLI subagents in parallel, tracks them through shared memory and verifies each result.

    1.3k GitHub stars~3.1k tokensUpdated yesterday
    Auto-check passed

  • Architecture Decisions and ADRs

    first-fluke/oh-my-agent

    Evaluates system boundaries and tradeoffs and writes architecture recommendations, option comparisons or ADRs, with a Mermaid diagram when structure changes.

    1.3k GitHub stars~2.6k tokensUpdated yesterday
    Auto-check passed

  • OMA Backend Agent

    first-fluke/oh-my-agent

    Backend specialist for APIs, database work, authentication and migrations that follows clean architecture with router, service and repository layers.

    1.3k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

  • oma Bootstrap

    first-fluke/oh-my-agent

    Installs or checks the oma CLI and its runtimes (bun, uv, serena) in a fresh workspace so that oma-* skills can run their commands.

    1.3k GitHub stars~719 tokensUpdated yesterday
    Auto-check passed

  • Design-First Brainstorm

    first-fluke/oh-my-agent

    Explores intent, constraints and alternative approaches before any planning, working through questions one at a time and saving an approved design for later steps.

    1.3k GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Oma Debug

What does Oma Debug do?

Bug diagnosis and fixing specialist - analyzes errors, identifies root causes, provides fixes, and writes regression tests. Oma Debug is an agent skill from first-fluke/oh-my-agent. Bug diagnosis and fixing specialist - analyzes errors, identifies root causes, provides fixes, and writes regression tests.

When should I use Oma Debug?

Oma Debug fits situations like: regression work; tasks that involve Root cause analysis; tasks that involve Debugging.

How do I install Oma Debug in Claude Code?

Run `npx skills add first-fluke/oh-my-agent --skill oma-debug -a claude-code`. Or copy the skill folder (benchmarks/runs/oma/.agents/skills/oma-debug in first-fluke/oh-my-agent) into .claude/skills/oma-debug in your project. Claude Code loads it when a task matches its description.

How do I install Oma Debug in Codex?

Run `npx skills add first-fluke/oh-my-agent --skill oma-debug -a codex`. Or copy the skill folder (benchmarks/runs/oma/.agents/skills/oma-debug in first-fluke/oh-my-agent) into .agents/skills/oma-debug in your project. Codex loads it when a task matches its description.

Can I use Oma Debug 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 first-fluke/oh-my-agent --skill oma-debug -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/oma-debug, .gemini/skills/oma-debug, .github/skills/oma-debug and .opencode/skills/oma-debug in your project.

What does Oma Debug need to run?

Going by SKILL.md and its folder, Oma Debug needs the command-line tools its instructions call (rg).

Does Oma Debug 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 Oma Debug 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 Oma Debug use?

Oma Debug 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 Oma Debug use?

About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Oma Debug?

Skills that share tags, products or a category with Oma Debug: OpenROAD Bug Fixer (The-OpenROAD-Project/OpenROAD, 3.2k stars), Triagebot Action Bug Triage (withastro/astro, 63k stars), Root Cause Debugging (jsmastery-pro/skills, 1.4k stars) and Issue Tracer (ZaxbyHub/opencode-swarm, 488 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Oma Debug?

first-fluke (a GitHub organization) maintains it in first-fluke/oh-my-agent, which has 1,335 GitHub stars. The repository holds 57 skills in this directory. The repository was last updated on October 6, 2026.

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