oma-debug
/oma-debug
Diagnose a reproducible failure, fix its cause, and verify the regression. Use for crashes, incorrect behavior, and failing tests.
- Author
- first-fluke ↗
- Repository
- oh-my-agent ↗
- Licence
- MIT
- Last repository change
- 24.10.2026
Assessment and security
- Files in this package
- 7
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Diagnose a reproducible failure, fix its cause, and verify the regression. Use for crashes, incorrect behavior, and failing tests.
Original author description
Diagnose a reproducible failure, fix its cause, and verify the regression. Use for crashes, incorrect behavior, and failing tests.
How it works
- Scheduling
- Structural Flow
- Logical Operations
- References
SKILL.md preview
--- 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 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 ### 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 | ### 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 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/` ### 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.md` - Checklist (pre-submit self-verification): `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 (investigation guide, used during Steps 1-2): `resources/debugging-checklist.md` - Context loading: `../_shared/core/context-loading.md` - Context budget: `../_shared/core/context-budget.md` - Lessons learned: `../_shared/core/lessons-learned.md` (matching prior failure or requested retrospective) - Observability handoff: `../oma-observability/SKILL.md` §Integrations — traces/logs by `trace_id`, 6-dim forensics
Files in this package (7)
- SKILL.md 6 KB
- resources/bug-report-template.md 7 KB
- resources/checklist.md 1 KB
- resources/common-patterns.md 15 KB
- resources/debugging-checklist.md 10 KB
- resources/error-playbook.md 3 KB
- resources/execution-protocol.md 2 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · first-fluke/oh-my-agent | 100 | MIT |
| first-fluke/oh-my-agent | 100 | MIT |
| first-fluke/oh-my-agent | 100 | MIT |
Identical content appears in 2 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 6395d9768e4e (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 86vibe-debug
Diagnose and fix a reproducible failure in an existing project. Use for crashes, broken behavior, or failing checks, not greenfield planning. - 81shadow-debug
Diagnose and fix a reported failure using a reproducible symptom, a focused cause investigation, and regression verification. Use for broken behavior, errors, crashes, or failing checks. - 100decant-debug
Diagnose a failure from reproducible evidence and isolate its root cause. Use for regressions, flaky behavior, stuck automation, or failed checks; edit only when the user also asked for a fix. - 100debug
Diagnose a failing test, build, crash, regression, or unexpected behavior without editing source. Reproduce the symptom, test hypotheses, identify the supported root cause, and hand off a repair. Use for /debug, root-cause investigation, or questions about why something is broken. - 86debug
Use when something fails or behaves wrong and the cause is not obvious - an error, traceback, failing test, crash, hang or wrong output. Systematic reproduce, isolate, fix, verify. - 100diagnosis-evidence
Make a diagnosis prove it measured what it claims — before reporting a cause, a "not a regression", a mutation check, or a passing verification. Use when debugging a failing test, a CI failure, a flake, or verifying a fix by hand.