Ce Report Bug
Skill Verified ActiveReport a bug in the compound-engineering plugin
To streamline the bug reporting process for the compound-engineering plugin, ensuring maintainers receive detailed and actionable information.
Features
- Collects structured bug information from the user
- Gathers OS, plugin, and agent version details
- Formats bug reports into a markdown structure
- Creates GitHub issues using the GitHub CLI
- Provides clear error handling and fallback mechanisms
Use Cases
- Reporting a broken command or agent within the compound-engineering plugin
- Documenting installation or configuration issues with the plugin
- Providing detailed bug reports to the maintainer for faster resolution
Non-Goals
- Fixing the reported bugs directly
- Managing GitHub issues beyond creation
- Collecting personal user information or private code
Scope
- info:Dry-run previewWhile creating a GitHub issue is a state-changing operation, there is no explicit `--dry-run` flag. The skill prompts the user for all information, which acts as a form of pre-confirmation.
Practical Utility
- info:Usage examplesWhile the skill itself is straightforward, explicit end-to-end examples of its invocation and output are not provided in the SKILL.md, though the README offers general usage examples for the plugin.
Installation
First, add the marketplace
/plugin marketplace add EveryInc/compound-engineering-plugin/plugin install compound-engineering@compound-engineering-pluginQuality Score
VerifiedTrust Signals
Similar Extensions
Github
100Use gh for GitHub issues, PR status, CI/logs, comments, reviews, releases, and API queries.
Project Session Manager
100Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions
Oh My Claudecode
100Process-first advisor routing for Claude, Codex, or Gemini via `omc ask`, with artifact capture and no raw CLI assembly
Use My Browser
100Use when work depends on the user's live browser session or visible rendered state rather than static fetches, especially for browser debugging contexts or DevTools-selected elements or requests, logged-in dashboards or CMS flows, localhost apps, forms, uploads, downloads, media inspection, DOM or iframe inspection, Shadow DOM, or browser failures that look like soft 404s, auth walls, anti-bot checks, or rate limits.
Telegram Crabbox E2e Proof
100Use when reviewing, reproducing, or proving OpenClaw Telegram behavior with a real Telegram user on Crabbox, including PR review workflows that need an agent-controlled Telegram Desktop recording, TDLib user-driver commands, Convex-leased credentials, WebVNC observation, and motion-trimmed artifacts.
Openclaw Testing
100Choose, run, rerun, or debug OpenClaw tests, CI checks, Docker E2E lanes, release validation, and the cheapest safe verification path.