ce-report-bug

Automate structured bug reporting for the ce plugin via GitHub issues.

2|Updated May 8, 2026
One-click install
npx skills add https://github.com/xotong/claude-marketplace --skill ce-report-bug-xotong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-report-bug
Source: https://github.com/xotong/claude-marketplace/tree/main/plugins/compound-engineering/skills/ce-report-bug
Command: npx skills add https://github.com/xotong/claude-marketplace --skill ce-report-bug-xotong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bug reporting for the compound-engineering plugin is often manual and inconsistent. This skill guides users to collect complete bug details, environment data, and reproduce steps, then formats them into a ready-to-submit report.

Core Features & Use Cases

  • Structured bug intake: captures category, component, steps, environment, and messages in a consistent format.
  • GitHub integration: uses the gh CLI to create issues in the plugin repository with a formatted body.
  • Validation and feedback: prompts for missing fields and confirms submission with the issue URL.

Quick Start

Run /ce-report-bug and follow the prompts to report a bug.

Frequently Asked Questions about ce-report-bug

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

FAQPage Schema
How do I automate structured bug reporting for GitHub issues?

Automating structured bug reporting involves capturing category, component, reproduction steps, and environment data, then formatting these details and creating a GitHub issue. This skill uses the gh CLI to validate fields and submit the formatted report directly to the plugin repository.

What is the best way to ensure complete environment info is captured in a bug report?

Capturing complete environment info in a bug report requires a structured intake process that prompts for specific system details and reproduction steps. This skill guides users through data collection, ensuring all necessary environment variables and error messages are included before submission.

Does this bug reporting automation work with the gh CLI for GitHub issue creation?

Yes, this bug reporting automation integrates directly with the gh CLI to create GitHub issues. It formats the collected bug data into a structured body and uses the CLI to submit the issue, providing validation, fallback handling, and a confirmation URL upon success.

Can I use this skill to report bugs across different bug categories for software engineering projects?

Yes, you can use this skill to report bugs across various bug categories within software engineering projects. It applies to developers reporting issues by guiding the collection of category, component, and environment data, ensuring a consistent format for every bug report submitted.

What happens if required fields are missing during automated bug report generation?

If required fields are missing during automated bug report generation, the skill prompts the user to provide the missing information. It implements validation and feedback mechanisms to ensure the bug report is complete before attempting to create the GitHub issue via the CLI.

Why should I use a structured bug intake process instead of manual issue tracking?

A structured bug intake process eliminates the inconsistency of manual issue tracking by enforcing a uniform format for categories, environment data, and reproduction steps. This ensures GitHub issues contain all necessary debugging context, reducing back-and-forth communication.