report-bug-ce

Collect structured bug data and generate a labeled GitHub issue via GitHub CLI.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/yxc023/agent-config-studio --skill report-bug-ce-yxc023
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: report-bug-ce
Source: https://github.com/yxc023/agent-config-studio/tree/main/.opencode/skills/report-bug-ce
Command: npx skills add https://github.com/yxc023/agent-config-studio --skill report-bug-ce-yxc023

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Bug reporting for the compound-engineering plugin is often manual, fragmented, and hard to standardize; this skill provides a consistent workflow to collect structured bug data and create a GitHub issue for triage and fixes.

## Core Features & Use Cases

  • Collects structured bug details including category, component, steps to reproduce, environment, and error messages.
  • Formats a standardized bug report and submits it via GitHub CLI to a dedicated repository with labels.
  • Use Case: A developer encounters a failing plugin command and uses /report-bug-ce to generate a reproducible bug report and automatically file an issue.

### Quick Start Run the /report-bug-ce command and follow the prompts to generate a formatted bug report and open a GitHub issue.

Frequently Asked Questions about report-bug-ce

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I report a bug to GitHub from the command line for a plugin issue?▼

You can report a bug by running the /report-bug-ce command to collect structured details like category, steps to reproduce, and environment, which then generates a standardized GitHub issue with proper labels via the GitHub CLI.

What is the best way to capture environment diagnostics for a structured bug report?▼

Capturing environment diagnostics for a bug report involves collecting structured data including the specific component, error messages, and environment details. This skill automates the deterministic steps to gather this information for the compound-engineering plugin.

Does this bug reporting workflow require the GitHub CLI to create issues?▼

Yes, this bug reporting workflow requires the GitHub CLI to submit the formatted bug report. It invokes the GitHub CLI to automatically create the issue in a dedicated repository with the appropriate triage labels.

Can I use this to file agent or server issues, or is it only for plugin commands?▼

You can use this to file agent, command, skill, or server issues. The workflow applies to developers and operators encountering various compound-engineering plugin problems and needs an end-to-end bug-report workflow including environment capture.

Why should I use a structured bug reporting skill instead of manually writing a GitHub issue?▼

You should use a structured bug reporting skill because manual reporting is often fragmented and hard to standardize. This skill provides a consistent workflow to collect bug data and create a GitHub issue for efficient triage and fixes.

What information do I need to provide when reporting a failing plugin command?▼

When reporting a failing plugin command, you need to provide structured bug details including the issue category, affected component, steps to reproduce, environment information, and specific error messages to generate a reproducible bug report.