From compound-engineering
Guides users to report bugs in compound-engineering plugin by gathering details, env info, formatting Markdown, and creating GitHub issues.
npx claudepluginhub everyinc/compound-engineering-plugin --plugin compound-engineeringThis skill uses the workspace's default tool permissions.
Report bugs encountered while using the compound-engineering plugin. This skill gathers structured information and creates a GitHub issue for the maintainer.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Report bugs encountered while using the compound-engineering plugin. This skill gathers structured information and creates a GitHub issue for the maintainer.
Ask the user the following questions (using the platform's blocking question tool — e.g., AskUserQuestion in Claude Code, request_user_input in Codex, ask_user in Gemini — or present numbered options and wait for a reply):
Question 1: Bug Category
Question 2: Specific Component
Question 3: What Happened (Actual Behavior)
Question 4: What Should Have Happened (Expected Behavior)
Question 5: Steps to Reproduce
Question 6: Error Messages
Automatically gather environment details. Detect the coding agent platform and collect what is available:
OS info (all platforms):
uname -a
Plugin version: Read the plugin manifest or installed plugin metadata. Common locations:
~/.claude/plugins/installed_plugins.json.codex/plugins/ or project configAgent CLI version: Run the platform's version command:
claude --versioncodex --versionIf any of these fail, note "unknown" and continue — do not block the report.
Create a well-structured bug report with:
## 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*
Use the GitHub CLI to create the 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"
Note: If labels don't exist, create without labels:
gh issue create \
--repo EveryInc/compound-engineering-plugin \
--title "[compound-engineering] Bug: [Brief description]" \
--body "[Formatted bug report]"
After the issue is created:
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.
gh CLI is not installed or not authenticated: prompt the user to install/authenticate firstThis skill does NOT collect:
Only technical information about the bug is included in the report.