Conversation
Add the bug-investigator agent adapted from the engineering-recipes template with Goonj-specific values for CiviCRM/WordPress debugging. Register it in CLAUDE.md alongside the existing implementation-planner. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
WalkthroughThree documentation files are added to define a new bug-investigator agent: an agent specification with a detailed investigation workflow, a memory file documenting codebase patterns and code patterns to watch for, and an index entry in CLAUDE.md. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
No actionable comments were generated in the recent review. 🎉 Tip Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord. Comment |
Summary
bug-investigatorClaude Code agent adapted from the engineering-recipes template with all placeholders replaced with Goonj-specific values (CiviCRM, WordPress, PHP 8.x, MySQL)CLAUDE.mdalongside the existingimplementation-plannerTest plan
.claude/agents/bug-investigator.mdhas correct YAML frontmatter (model: opus,color: red,memory: project){{PLACEHOLDER}}values have been replaced with Goonj-specific contentCLAUDE.mdCustom Agents table includes bothimplementation-plannerandbug-investigator🤖 Generated with Claude Code
Summary by CodeRabbit