report-bug-ce

Collect bug details and create a GitHub issue for the compound-engineering plugin.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/jaydubya818/New_baseline --skill report-bug-ce-jaydubya818
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: report-bug-ce
Source: https://github.com/jaydubya818/New_baseline/tree/main/skills/compound-engineering/plugins/compound-engineering/skills/report-bug-ce
Command: npx skills add https://github.com/jaydubya818/New_baseline --skill report-bug-ce-jaydubya818

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gathers structured bug information and automatically creates a GitHub issue for the compound-engineering plugin, reducing back-and-forth and speeding triage.

Core Features & Use Cases

  • Collects bug category, component and reproduction steps from the user.
  • Automatically formats a comprehensive bug report and submits it as a GitHub issue via the GitHub CLI.
  • Provides a submission confirmation with the issue URL to close the loop with maintainers.

Quick Start

Run /report-bug-ce and follow the prompts to file a 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 automatically create a GitHub issue for a bug report?

Automating bug reporting to GitHub involves collecting category, component, and reproduction steps into a structured format, then submitting via the GitHub CLI. This skill handles that workflow and returns a confirmation URL.

What is the best way to structure a bug report for GitHub issue tracking?

The best way to structure a bug report for GitHub issue tracking is to enforce a format containing the bug category, affected component, and steps to reproduce. This skill automates that formatting to speed up triage.

Do I need the GitHub CLI installed to automate issue creation?

You do not strictly need the GitHub CLI installed to automate issue creation, as this skill provides fallbacks if the CLI is missing. However, using the gh CLI is the primary submission method for structured bug reports.

How does automated bug reporting work within a plugin ecosystem?

Automated bug reporting within a plugin ecosystem works by gathering environment data and categorizing issues by specific plugin components. This skill standardizes the end-to-end reporting process before submitting to GitHub.

What happens if the GitHub CLI is missing when submitting a bug report?

If the GitHub CLI is missing when submitting a bug report, the skill uses built-in fallbacks to handle the issue creation process. It still collects the structured data but adapts the submission method accordingly.