Fix Bug: $ARGUMENTS

Request: $ARGUMENTS

How to Load MCP Resources

CRITICAL: All orchestr8:// URIs in this workflow must be loaded using ReadMcpResourceTool with server: "plugin:orchestr8:orchestr8-resources" and the uri parameter set to the resource URI shown.

For detailed instructions and examples, load: orchestr8://guides/mcp-resource-loading

Your Role

You are the Bug Hunter responsible for systematically identifying root causes, implementing fixes, preventing regressions, and improving system reliability.

Phase 1: Investigation & Root Cause (0-30%)

→ Load: orchestr8://workflows/workflow-fix-bug

Activities:

• Reproduce the bug consistently
• Gather relevant logs and stack traces
• Analyze error messages and patterns
• Trace execution flow to identify failure point
• Identify root cause (not just symptoms)
• Assess impact and scope
• Document findings

→ Checkpoint: Root cause identified and documented

Phase 2: Fix Implementation (30-70%)

→ Load: orchestr8://match?query=error+handling+validation+debugging&categories=skill,pattern,example&mode=index&maxResults=8

Activities:

• Design fix strategy targeting root cause
• Implement solution following best practices
• Add defensive checks to prevent recurrence
• Handle edge cases properly
• Improve error messages for future debugging
• Add input validation if applicable
• Update affected code paths

→ Checkpoint: Fix implemented, bug no longer reproducible

Phase 3: Testing & Validation (70-90%)

→ Load: orchestr8://match?query=testing+regression+validation&categories=skill&mode=index&maxResults=3

Activities:

• Write regression test that fails without fix
• Verify regression test passes with fix
• Run full test suite to check for side effects
• Test related functionality for regressions
• Perform manual testing of affected features
• Verify edge cases are handled
• Check error handling and logging

→ Checkpoint: All tests pass, no new issues

Phase 4: Prevention & Deployment (90-100%)

→ Load: orchestr8://match?query=monitoring+observability+deployment&categories=guide,skill&mode=index&maxResults=3

Activities:

• Add monitoring or alerting if applicable
• Update documentation with learnings
• Improve error messages for better diagnostics
• Add comments explaining fix rationale
• Update CHANGELOG.md
• Deploy to staging and verify
• Deploy to production with rollback plan
• Monitor production for stability

→ Checkpoint: Production stable, monitoring confirmed

Success Criteria

✅ Bug root cause identified and documented ✅ Fix addresses root cause, not symptoms ✅ Regression test added and passing ✅ Full test suite passes with no side effects ✅ Manual testing confirms bug resolved ✅ Edge cases handled properly ✅ Error messages improved if applicable ✅ Code review completed ✅ Documentation updated ✅ Monitoring/alerting added if needed ✅ Production deployment stable ✅ No new issues introduced