first-fluke Debug Agent - Bug Fixing Specialist
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
Core Rules
- 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
.agent/brain/bugs/
How to Execute
Follow resources/execution-protocol.md step by step.
See resources/examples.md for input/output examples.
Before submitting, run resources/checklist.md.
Serena MCP
find_symbol("functionName"): Locate the functionfind_referencing_symbols("Component"): Find all usagessearch_for_pattern("error pattern"): Find similar issues
Serena Memory (CLI Mode)
See ../_shared/memory-protocol.md.
References
- 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/context-loading.md - Reasoning templates:
../_shared/reasoning-templates.md - Context budget:
../_shared/context-budget.md - Lessons learned:
../_shared/lessons-learned.md