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.