report-bug

Collect structured bug details and submit GitHub issues for the compound-engineering plugin.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/drhazemibclc/plate --skill report-bug-drhazemibclc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: report-bug
Source: https://github.com/drhazemibclc/plate/tree/main/.codex/skills/report-bug
Command: npx skills add https://github.com/drhazemibclc/plate --skill report-bug-drhazemibclc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The bug-reporting skill standardizes bug reporting for the compound-engineering plugin by guiding users to provide complete details and automating GitHub issue creation.

Core Features & Use Cases

  • Step-by-step bug information collection
  • Automated GitHub issue formatting and submission
  • Reproducible steps and environment capture for accurate triage

Quick Start

Run the /report-bug command to begin collecting details and submit the resulting report as a GitHub issue.

Frequently Asked Questions about report-bug

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

FAQPage Schema
How do I report a bug to a GitHub repository using automated issue creation?

To report a bug to a GitHub repository, this skill gathers structured information and formats it into a GitHub issue. It collects issue type, component, environment, reproduction steps, and expected behavior, then submits the issue automatically.

Do I need GitHub CLI access to automate bug reporting?

Yes, GitHub CLI access is required to automate bug reporting and issue submission. The skill uses the GitHub CLI to create and submit the formatted issue report directly to the target repository.

What information do I need to provide for consistent bug triage?

For consistent bug triage, you need to provide the issue type, component, description, environment details, steps to reproduce, and expected versus actual behavior. This structured information ensures accurate and consistent triage.

How does automated bug tracking format steps to reproduce for GitHub issues?

Automated bug tracking formats steps to reproduce by guiding you through structured information collection. It captures your reproduction steps and environment details, then formats them into a standardized GitHub issue report for submission.

Can I categorize plugin bug reports by issue type and component?

Yes, you can categorize plugin bug reports by issue type and component. The skill supports categorizing bugs by these fields during the collection process to ensure structured and consistent GitHub issue creation.

Are there limitations when submitting bug reports to the compound-engineering plugin?

The skill is limited to submitting bug reports specifically to the EveryInc/compound-engineering-plugin repository. It requires both GitHub CLI access and user-provided details to successfully create and submit the issue.