report-bug-ce

Collect structured bug details and environment context for compound-engineering plugin issues.

Updated Nov 11, 2023
One-click install
npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill report-bug-ce
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: report-bug-ce
Source: https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb/tree/main/.opencode/skills/ce/report-bug-ce
Command: npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill report-bug-ce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the friction of collecting fragmented bug details for the compound-engineering plugin by guiding the user through a structured interview and compiling a complete report ready for maintainers.

Core Features & Use Cases

  • Structured Interviews: Ask six targeted questions covering category, component, actual behavior, expectations, reproduction steps, and error output so nothing critical is missed.
  • Environment Snapshot: Automatically gather OS information, plugin version, and agent CLI version to provide essential diagnostics alongside the user’s answers.
  • GitHub Issue Automation: Format everything into a cohesive markdown report and open a GitHub issue with labels for the compound-engineering plugin, making it easy for maintainers to act.
  • Use Case: When a command fails inside the compound-engineering agent with confusing output, use this Skill to gather all context, format the bug narrative, and file the issue without manual formatting.

Quick Start

Use the report-bug-ce skill to ask the six bug questions, collect environment details, and submit a structured GitHub issue for the compound-engineering plugin.

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 in the compound-engineering plugin?

To report a bug in the compound-engineering plugin, this Skill guides you through a structured interview covering symptoms, reproduction steps, and error output, then compiles everything into a formatted GitHub issue.

What information do I need to file a GitHub issue for compound-engineering agents?

Filing a GitHub issue for compound-engineering agents requires categorized symptoms, actual behavior, expectations, reproduction steps, error output, and an environment snapshot including OS, plugin, and CLI versions.

Can I automate environment collection when troubleshooting compound-engineering commands?

Yes, you can automate environment collection when troubleshooting compound-engineering commands by using this Skill to automatically gather OS information, plugin version, and agent CLI version alongside your bug details.

Does the bug reporting workflow format issues directly for GitHub?

Yes, the bug reporting workflow formats your structured answers and environment context into a cohesive markdown report with appropriate labels, then invokes the gh CLI to open a GitHub issue directly.

What's the best way to document a failing compound-engineering MCP server component?

The best way to document a failing compound-engineering MCP server component is to answer six targeted questions about the failure category and behavior, letting the Skill compile a complete diagnostic report for maintainers.