القائمة
Reproduce and investigate a bug using logs, console inspection, and browser screenshots
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Optimize Claude Code permissions by finding safe Bash commands from session history and auto-applying them to settings.json. Can run from any coding agent but targets Claude Code specifically. Use when experiencing permission fatigue, too many permission prompts, wanting to optimize permissions, or needing to set up allowlists. Triggers on "optimize permissions", "reduce permission prompts", "allowlist commands", "too many permission prompts", "permission fatigue", "permission setup", or complaints about clicking approve too often.
Browser automation using Vercel's agent-browser CLI. Use when you need to interact with web pages, fill forms, take screenshots, or scrape data. Alternative to Playwright MCP - uses Bash commands with ref-based element selection. Triggers on "browse website", "fill form", "click button", "take screenshot", "scrape page", "web automation".
[BETA] Transform feature descriptions or requirements into structured implementation plans grounded in repo patterns and research. Use when the user says 'plan this', 'create a plan', 'write a tech plan', 'plan the implementation', 'how should we build', 'what's the approach for', 'break this down', or when a brainstorm/requirements document is ready for technical planning. Best when requirements are at least roughly defined; for exploratory or ambiguous requests, prefer ce:brainstorm first.
Transform feature descriptions into well-structured project plans following conventions
Perform exhaustive code reviews using multi-agent analysis, ultra-thinking, and worktrees
Create or edit Claude Code skills with expert guidance on structure and best practices
| name | reproduce-bug |
| description | Reproduce and investigate a bug using logs, console inspection, and browser screenshots |
| argument-hint | [GitHub issue number] |
| disable-model-invocation | true |
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: