averello/compound-engineering-plugin-mirror

mirror of https://github.com/EveryInc/compound-engineering-plugin.git synced 2026-09-28 17:12:57 +02:00

Files

T

Kieran KlaassenandClaude Opus 4.6 a248363de7 [2.31.0] Reduce context token usage by 79%, include recent community contributions

The plugin was consuming 316% of Claude Code's description character budget
(~50,500 chars vs 16,000 limit), causing components to be silently excluded.
Now at 65% (~10,400 chars) with all components visible.

Changes:
- Trim all 29 agent descriptions (move examples to body)
- Add disable-model-invocation to 18 manual commands
- Add disable-model-invocation to 6 manual skills
- Include recent community contributions in changelog
- Fix component counts (29 agents, 24 commands, 18 skills)

Contributors: @trevin, @terryli, @robertomello, @zacwilliams,
@aarnikoskela, @samxie, @davidalley

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-02-08 15:34:08 -08:00

3.0 KiB

Raw Permalink Blame History

name, description, argument-hint, disable-model-invocation

name	description	argument-hint	disable-model-invocation
reproduce-bug	Reproduce and investigate a bug using logs, console inspection, and browser screenshots	[GitHub issue number]	true

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:

Task rails-console-explorer(issue_description)
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 with Playwright

If the bug is UI-related or involves user flows, use Playwright to visually reproduce it:

Step 1: Verify Server is Running

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.

Step 2: Navigate to Affected Area

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({})

Step 3: Capture Screenshots

Take screenshots at each step of reproducing the bug:

mcp__plugin_compound-engineering_pw__browser_take_screenshot({ filename: "bug-[issue]-step-1.png" })

Step 4: Follow User Flow

Reproduce the exact steps from the issue:

Read the issue's reproduction steps
Execute each step using Playwright:
- browser_click for clicking elements
- browser_type for filling forms
- browser_snapshot to see the current state
- browser_take_screenshot to capture evidence

Check for console errors:

mcp__plugin_compound-engineering_pw__browser_console_messages({ level: "error" })

Step 5: Capture Bug State

When you reproduce the bug:

Take a screenshot of the bug state
Capture console errors
Document the exact steps that triggered it

mcp__plugin_compound-engineering_pw__browser_take_screenshot({ filename: "bug-[issue]-reproduced.png" })

Phase 3: Document Findings

Reference Collection:

Document all research findings with specific file paths (e.g., app/services/example_service.rb:42)
Include screenshots showing the bug reproduction
List console errors if any
Document the exact reproduction steps

Phase 4: Report Back

Add a comment to the issue with:

Findings - What you discovered about the cause
Reproduction Steps - Exact steps to reproduce (verified)
Screenshots - Visual evidence of the bug (upload captured screenshots)
Relevant Code - File paths and line numbers
Suggested Fix - If you have one

3.0 KiB Raw Permalink Blame History