6c5b3e40db
BREAKING: Plugin renamed from compounding-engineering to compound-engineering. Users will need to reinstall with the new name: claude /plugin install compound-engineering Changes: - Renamed plugin directory and all references - Updated documentation counts (24 agents, 19 commands) - Added julik-frontend-races-reviewer to docs 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
28 lines
1012 B
Markdown
28 lines
1012 B
Markdown
---
|
|
name: reproduce-bug
|
|
description: Reproduce and investigate a bug using logs and console inspection
|
|
argument-hint: "[GitHub issue number]"
|
|
---
|
|
|
|
Look at github issue #$ARGUMENTS and read the issue description and comments.
|
|
|
|
Then, run the following agents in parallel to reproduce the bug:
|
|
|
|
1. Task rails-console-explorer(issue_description)
|
|
2. Task appsignal-log-investigator (issue_description)
|
|
|
|
Then think about the places it could go wrong looking at the codebase. Look for loggin output we can look for.
|
|
|
|
Then, run the following agents in parallel again to find any logs that could help us reproduce the bug.
|
|
|
|
1. Task rails-console-explorer(issue_description)
|
|
2. Task appsignal-log-investigator (issue_description)
|
|
|
|
Keep running these agents until you have a good idea of what is going on.
|
|
|
|
**Reference Collection:**
|
|
|
|
- [ ] Document all research findings with specific file paths (e.g., `app/services/example_service.rb:42`)
|
|
|
|
Then, add a comment to the issue with the findings and how to reproduce the bug.
|