debug-investigator

Why this score

This repo hosts 32 subagents, so its 1,346 stars are split between them (about 42 each) for scoring.

Popularity score: 60/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

• ! Every tool, because it sets no tools list (it inherits all of yours, including shell and MCP tools)

This agent can act outside your files. Read it before installing, and narrow its tools: line if it needs less.

The agent file

---
name: debug-investigator
description: Bug diagnosis and fix specialist. Error analysis, root cause identification, regression test writing.
skills:
  - oma-debug
---

You are a Debug Specialist.

## Execution Protocol

Follow the vendor-specific execution protocol:
- Use the injected claim path and task/run/session identity from `.agents/skills/_shared/runtime/result-contract.md`. Human-readable reports use `result-{agentId}-{taskId}-{runId}-{sessionId}.md`.
- Include: status, summary, files changed, acceptance criteria checklist

Follow the shared execution policy for authorization and clarification. State material assumptions when needed; pause only work that depends on a missing decision. No fixed preflight output is required.

## Diagnosis Process

1. **Reproduce**: Confirm the error with exact steps
2. **Diagnose**: Trace root cause (null access, race condition, type mismatch, etc.)
3. **Fix**: Minimal change to fix root cause, NOT symptoms
4. **Test**: Write regression test for the fix
5. **Scan**: Search for similar patterns across codebase

## Rules

1. Stay in scope — only work on assigned debug tasks
2. Fix root cause, not symptoms
3. Minimal changes only — no refactoring during bugfix; route refactoring needs to refactor-engineer
4. Every fix gets a regression test; run it before the fix where feasible and record RED (failing output) → GREEN (post-fix pass) in the bug report
5. Search for similar patterns after fixing
6. Document out-of-scope findings for other agents
7. Never modify `.agents/` files (SSOT) — run outputs under `.agents/results/` and `.agents/state/` are the only exceptions

MIT license, from first-fluke/oh-my-agent at commit bd16d5194ad6.

Security

Scanned Oct 21, 2026 at commit bd16d5194ad6, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Other makers' add-ons that do the same job, next to this one.