From compound-engineering
Reproduces GitHub bugs via Rails log/console analysis, Playwright browser automation for screenshots/console errors, documents findings/code paths, and comments on the issue.
npx claudepluginhub gvkhosla/compound-engineering-pi --plugin compound-engineering[GitHub issue number]# Reproduce Bug Command Look at github issue #$ARGUMENTS and read the issue description and comments. ## Phase 1: Log Investigation Run the following agents in parallel to investigate the bug: 1. Task rails-console-explorer(issue_description) 2. Task appsignal-log-investigator(issue_description) Think about the places it could go wrong looking at the codebase. Look for logging output we can look for. Run the agents again to find any logs that could help us reproduce the bug. Keep running these agents until you have a good idea of what is going on. ## Phase 2: Visual Reproduction wit...
/reproduce-bugReproduces GitHub issue bugs using Rails console/AppSignal logs, Playwright browser inspection/screenshots, documents findings with code refs, and adds issue comment.
/debugInvestigates a bug by reproducing it, tracing through code, finding the root cause, and documenting findings. Accepts a bug ID, file path, or symptom description.
/hatch3r-debugInstruments codebase with strategic debug logging, collects runtime logs from user, performs root cause analysis, implements fix, and cleans up artifacts.
/debugInvestigates bugs scientifically with 7 techniques: reproduces failures, gathers evidence, isolates root cause, produces analysis document with file:line and fix suggestion. Supports --error, --test, --bisect flags.
/debugPerforms 4-phase systematic debugging on a bug: reproduce, root cause analysis with tests, TDD fix, and defense-in-depth verification.
/debugDebugs and fixes bugs end-to-end: checks context and known issues, reproduces, investigates root cause, test-first fix, and creates PR.
Share bugs, ideas, or general feedback.
Look at github issue #$ARGUMENTS and read the issue description and comments.
Run the following agents in parallel to investigate the bug:
Think about the places it could go wrong looking at the codebase. Look for logging output we can look for.
Run the agents again to find any logs that could help us reproduce the bug.
Keep running these agents until you have a good idea of what is going on.
If the bug is UI-related or involves user flows, use Playwright to visually reproduce it:
mcp__plugin_compound-engineering_pw__browser_navigate({ url: "http://localhost:3000" })
mcp__plugin_compound-engineering_pw__browser_snapshot({})
If server not running, inform user to start bin/dev.
Based on the issue description, navigate to the relevant page:
mcp__plugin_compound-engineering_pw__browser_navigate({ url: "http://localhost:3000/[affected_route]" })
mcp__plugin_compound-engineering_pw__browser_snapshot({})
Take screenshots at each step of reproducing the bug:
mcp__plugin_compound-engineering_pw__browser_take_screenshot({ filename: "bug-[issue]-step-1.png" })
Reproduce the exact steps from the issue:
Read the issue's reproduction steps
Execute each step using Playwright:
browser_click for clicking elementsbrowser_type for filling formsbrowser_snapshot to see the current statebrowser_take_screenshot to capture evidenceCheck for console errors:
mcp__plugin_compound-engineering_pw__browser_console_messages({ level: "error" })
When you reproduce the bug:
mcp__plugin_compound-engineering_pw__browser_take_screenshot({ filename: "bug-[issue]-reproduced.png" })
Reference Collection:
app/services/example_service.rb:42)Add a comment to the issue with: