React Router Bug Fix Workflow
remix-run/react-router
Fixes a React Router bug reported in a GitHub issue end to end: fetching the issue, validating the reproduction, writing a failing test and implementing the fix on a new branch.
Diagnose a reproducible failure, fix its cause, and verify the regression.
Install Oma Debug
$ npx skills add first-fluke/oh-my-agent --skill oma-debug -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install first-fluke/oh-my-agent oma-debug --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/oma-debug .claude/skills/oma-debug && rm -rf skills-srcUse ~/.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/
Install the "oma-debug" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/skills/oma-debug into .claude/skills/oma-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-debug", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/first-fluke/oh-my-agent/tree/main/skills/oma-debugType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add first-fluke/oh-my-agent --skill oma-debug -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install first-fluke/oh-my-agent oma-debug --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/oma-debug .agents/skills/oma-debug && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "oma-debug" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/skills/oma-debug into .agents/skills/oma-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-debug", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add first-fluke/oh-my-agent --skill oma-debug -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install first-fluke/oh-my-agent oma-debug --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/oma-debug .cursor/skills/oma-debug && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "oma-debug" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/skills/oma-debug into .cursor/skills/oma-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-debug", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/first-fluke/oh-my-agent.git --path skills/oma-debug--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add first-fluke/oh-my-agent --skill oma-debug -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install first-fluke/oh-my-agent oma-debug --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/oma-debug .gemini/skills/oma-debug && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "oma-debug" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/skills/oma-debug into .gemini/skills/oma-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-debug", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install first-fluke/oh-my-agent oma-debugInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add first-fluke/oh-my-agent --skill oma-debug -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/oma-debug .github/skills/oma-debug && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "oma-debug" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/skills/oma-debug into .github/skills/oma-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-debug", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add first-fluke/oh-my-agent --skill oma-debug -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install first-fluke/oh-my-agent oma-debug --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/oma-debug .opencode/skills/oma-debug && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "oma-debug" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/skills/oma-debug into .opencode/skills/oma-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-debug", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
oma-debug- GitHub stars
- 1.3k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 744 words
- Files
- 7
- Skills in repo
- 57
- Repo updated
- First seen
- Licence
- MIT
At a glance
Diagnose a reproducible failure, fix its cause, and verify the regression.
- Works in 3 steps: Capture the reported symptom and… → Reproduce or establish the closest… → Identify affected files, tests, and…
- Incorrect behavior
- SKILL.md covers Scheduling, Structural Flow, Logical Operations and References
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Oma Debug is an agent skill from first-fluke/oh-my-agent. Diagnose a reproducible failure, fix its cause, and verify the regression. Use for crashes, incorrect behavior, and failing tests.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files (for example `resources/bug-report-template.md`, `resources/checklist.md` and `resources/common-patterns.md`).
It sits in Development, covering Failing and flaky tests 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
- Incorrect behavior
- Tasks that involve Failing and flaky tests
- Tasks that involve Debugging
Example prompts
- “/oma-debug”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Capture the reported symptom and suspected scope.
- Reproduce or establish the closest reliable failing signal.
- Identify affected files, tests, and related patterns.
What it can do on your machine
Read from SKILL.md and the folder at commit f65bbc0. 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
Oma Debug loads about 1.6k tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 744 words of instructions outside code blocks.
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 f65bbc0, republished under its MIT licence (© first-fluke). 744 words, ~1,610 tokens.
Download SKILL.mdSave it as
.claude/skills/oma-debug/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.- name
- oma-debug
- description
- Diagnose a reproducible failure, fix its cause, and verify the regression. Use for crashes, incorrect behavior, and failing tests.
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
- Capture the reported symptom and suspected scope.
- Reproduce or establish the closest reliable failing signal.
- Identify affected files, tests, and related patterns.
Scenes
- PREPARE: Gather symptoms, logs, reproduction path, and verification command.
- ACQUIRE: Read failing code, tests, references, and similar patterns.
- REASON: Isolate root cause and reject unsupported hypotheses.
- ACT: Apply minimal fix and regression test.
- VERIFY: Re-run failing and related checks.
- 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
Actions
| Action | SSL primitive | Evidence |
|---|---|---|
| Reproduce failure | CALL_TOOL | Test/runtime/log command |
| Search affected code | READ | Code, tests, symbols, references |
| Compare similar patterns | COMPARE | Pattern search |
| Infer root cause | INFER | Diagnostic reasoning |
| Write minimal fix | WRITE | Code patch |
| Write regression test | WRITE | Test patch |
| Verify behavior | VALIDATE | Tests/checks |
| Report result | NOTIFY | Root-cause summary |
Show full SKILL.md (307 more words)Show less
Tools and instruments
- Project test, lint, typecheck, runtime, and logging commands
- Configured code-intelligence symbol/reference/pattern search with native fallback
- Debugging checklist and bug report template
Canonical workflow path
Use the configured code-intelligence provider to locate files and inspect symbols
or content. For Serena, use find_file, search_for_pattern,
get_symbols_overview, and find_symbol. Native search is limited to the
provider exclusions and non-code paths permitted by the project's search policy.
Then run the smallest reproduction command first, establish the causal mechanism, and follow resources/execution-protocol.md for the diagnosis record when an OMA workflow is active. Add the regression test and re-run the failing check plus related tests.
Resource scope
| Scope | Resource target |
|---|---|
CODEBASE | Failing source, tests, and related patterns |
LOCAL_FS | Bug reports and result artifacts |
PROCESS | Reproduction and verification commands |
MEMORY | Hypotheses, 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
- Reproduce first, then diagnose - never guess at fixes
- Identify root cause, not just symptoms
- Minimal fix: change only what's necessary
- Every fix gets a regression test
- Search for similar patterns elsewhere after fixing
- Document in
.agents/results/bugs/
Code intelligence
Use the configured provider to locate the failing function, find callers, and search similar error patterns. Native search and scoped reads are supported fallbacks; see the shared capability contract.
References
Local code tools:
../_shared/core/code-intelligence.md(code search/navigation)Execution steps (follow for the selected task):
resources/execution-protocol.mdChecklist (pre-submit self-verification):
resources/checklist.mdError recovery:
resources/error-playbook.mdBug report template:
resources/bug-report-template.mdCommon patterns:
resources/common-patterns.mdDebugging checklist (investigation guide, used during Steps 1-2):
resources/debugging-checklist.mdContext loading:
../_shared/core/context-loading.mdContext budget:
../_shared/core/context-budget.mdLessons learned:
../_shared/core/lessons-learned.md(matching prior failure or requested retrospective)Observability handoff:
../oma-observability/SKILL.md§Integrations — traces/logs bytrace_id, 6-dim forensics
© 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 6 other files in 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/execution-protocol.md
Open the folder on GitHubat commit f65bbc0
Used in 1 other repository
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in first-fluke/oh-my-agent, which our catalogue first saw on October 7, 2026.
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Oma Debug this skillfirst-fluke/oh-my-agent | 1.3k | — | ~1.6k | Automated safety check: Pass | MIT | |
| React Router Bug Fix Workflowremix-run/react-router | 57k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Runtime Debugvercel/next.js | 143k | 1 repos | ~618 | Automated safety check: Pass | MIT | |
| Root Cause Debuggingjsmastery-pro/skills | 1.4k | — | ~1.8k | Automated safety check: Notes | MIT | |
| Superpowers Systematic Debuggingchristopherarter/superpowers-reasonix | 102 | — | ~2k | Automated safety check: Pass | MIT | |
| Minimal Code Fixcobusgreyling/loop-engineering | 11k | 1 repos | ~345 | Automated safety check: Notes | MIT |
Similar skills
- Official
Runtime Debug
vercel/next.js
Debug and verification workflow for runtime-bundle and module-resolution regressions.
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.
Superpowers Systematic Debugging
christopherarter/superpowers-reasonix
Any bug, failing or flaky test, or surprise behavior?. An agent skill from christopherarter/superpowers-reasonix.
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.
Fix The Class
joetawil7/first-pass
Bug-fix routine that fixes the whole class of bug, not just the reported instance.
More from first-fluke/oh-my-agent
All 57 skills in this repoOMA 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.
Oma Video
first-fluke/oh-my-agent
Create short, explainer, or recorded-demo videos through the OMA video CLI.
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.
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.
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.
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.
Related
Categories
Questions about Oma Debug
What does Oma Debug do?
Diagnose a reproducible failure, fix its cause, and verify the regression. Oma Debug is an agent skill from first-fluke/oh-my-agent. Diagnose a reproducible failure, fix its cause, and verify the regression.
When should I use Oma Debug?
Oma Debug fits situations like: incorrect behavior; tasks that involve Failing and flaky tests; 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 (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 (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?
SKILL.md names no scripts, command-line tools or credentials: Oma Debug is instructions for the agent only.
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.6k tokens (SKILL.md is roughly 6.4k 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: React Router Bug Fix Workflow (remix-run/react-router, 57k stars), Runtime Debug (vercel/next.js, 143k stars), Root Cause Debugging (jsmastery-pro/skills, 1.4k stars) and Superpowers Systematic Debugging (christopherarter/superpowers-reasonix, 102 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,338 GitHub stars. The repository holds 57 skills in this directory. The repository was last updated on October 8, 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.