Report a Compound Engineering Plugin Bug

Step 1: Gather Bug Information

AskUserQuestion

request_user_input

ask_user

• What type of issue are you experiencing?
• Options: Agent not working, Command not working, Skill not working, MCP server issue, Installation problem, Other

• Which specific component is affected?
• Ask for the name of the agent, command, skill, or MCP server

• Ask: "What happened when you used this component?"
• Get a clear description of the actual behavior

• Ask: "What did you expect to happen instead?"
• Get a clear description of expected behavior

• Ask: "What steps did you take before the bug occurred?"
• Get reproduction steps

• Ask: "Did you see any error messages? If so, please share them."
• Capture any error output

Step 2: Collect Environment Information

uname -a

• Claude Code:

  ~/.claude/plugins/installed_plugins.json

• Codex:

  .codex/plugins/

  or project config
• Other platforms: check the platform's plugin registry

• Claude Code:

  claude --version

• Codex:

  codex --version

• Other platforms: use the appropriate CLI version flag

Step 3: Format the Bug Report

## Bug Description

**Component:** [Type] - [Name]
**Summary:** [Brief description from argument or collected info]

## Environment

- **Plugin Version:** [from plugin manifest/registry]
- **Agent Platform:** [e.g., Claude Code, Codex, Copilot, Pi, Kilo]
- **Agent Version:** [from CLI version command]
- **OS:** [from uname]

## What Happened

[Actual behavior description]

## Expected Behavior

[Expected behavior description]

## Steps to Reproduce

1. [Step 1]
2. [Step 2]
3. [Step 3]

## Error Messages

[Any error output]

## Additional Context

[Any other relevant information]

---
*Reported via `/report-bug-ce` skill*

Step 4: Create GitHub Issue

gh issue create \
  --repo EveryInc/compound-engineering-plugin \
  --title "[compound-engineering] Bug: [Brief description]" \
  --body "[Formatted bug report from Step 3]" \
  --label "bug,compound-engineering"

gh issue create \
  --repo EveryInc/compound-engineering-plugin \
  --title "[compound-engineering] Bug: [Brief description]" \
  --body "[Formatted bug report]"

Step 5: Confirm Submission

1. Display the issue URL to the user
2. Thank them for reporting the bug
3. Let them know the maintainer (Kieran Klaassen) will be notified

Output Format

Bug report submitted successfully!

Issue: https://github.com/EveryInc/compound-engineering-plugin/issues/[NUMBER]
Title: [compound-engineering] Bug: [description]

Thank you for helping improve the compound-engineering plugin!
The maintainer will review your report and respond as soon as possible.

Error Handling

• If

  gh

  CLI is not installed or not authenticated: prompt the user to install/authenticate first
• If issue creation fails: display the formatted report so the user can manually create the issue
• If required information is missing: re-prompt for that specific field

Privacy Notice

• Personal information
• API keys or credentials
• Private code from projects
• File paths beyond basic OS info