report-bug-ce

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

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill report-bug-ce-andreicr1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: report-bug-ce
Source: https://github.com/Andreicr1/netz-analysis-engine/tree/main/.gemini/skills/report-bug-ce
Command: npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill report-bug-ce-andreicr1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report bugs encountered in the compound-engineering plugin by guiding users to collect structured information, gather environment data, and open a GitHub issue for the maintainer.

Core Features & Use Cases

  • Gather bug details (category, component, actual behavior, expected behavior, steps to reproduce, error messages).
  • Collect environment data (OS, plugin version, agent platform/version) and format a reproducible report.
  • Create GitHub issues on the EveryInc/compound-engineering-plugin repository and confirm submission.
  • Privacy-conscious handling: only basic environment information is collected.

Quick Start

Describe the bug you experienced; the system will collect details, format a 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 in the compound-engineering plugin to GitHub?

To report a bug in the compound-engineering plugin, provide the error details and the system collects your environment data, formats a structured report, and uses the gh CLI to auto-create a GitHub issue.

What information do I need to submit a GitHub issue for a plugin bug?

Submitting a GitHub issue for a plugin bug requires the bug category, affected component, actual and expected behavior, reproduction steps, error messages, and basic environment data like OS and plugin version.

Does the automated bug reporting process capture my full system environment data?

The automated bug reporting process is privacy-conscious and only collects basic environment information, specifically your OS, plugin version, and agent platform details to format the GitHub issue.

Can I use this tool to auto-create GitHub issues for any bug category?

Yes, you can auto-create GitHub issues across all bug categories by providing the specific component behavior, reproduction steps, and environment data required by the reporting workflow.

What is the best way to format reproducible steps for a GitHub issue report?

The best way to format reproducible steps for a GitHub issue is to input your raw error messages and behavior descriptions, which the system then structures into a formatted report for the maintainer.

Do I need the gh CLI installed to auto-submit bug reports to GitHub?

Yes, you need the gh CLI installed and configured, as the system relies on it to submit the formatted bug report and automatically open an issue on the EveryInc/compound-engineering-plugin repository.