skills.rest
kwam1na
kwam1naCOMMUNITY
Explore all skills by this author →
GitHub

ce-report-bug

Guide structured bug reporting and create GitHub issues via CLI.

Updated Sep 25, 2024
Search Tags:#automation#troubleshooting#plugin#bug-reporting#github-issues#compound-engineering#environment-info
One-click install
npx skills add https://github.com/kwam1na/athena --skill ce-report-bug-kwam1na
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce-report-bug
Source: https://github.com/kwam1na/athena/tree/main/.agents/skills/ce-report-bug
Command: npx skills add https://github.com/kwam1na/athena --skill ce-report-bug-kwam1na

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report bugs encountered while using the compound-engineering plugin. This skill guides you through collecting structured information and creates a GitHub issue for the maintainer.

Core Features & Use Cases

  • Guided questionnaire to capture Bug Category, Affected Component, Actual vs Expected Behavior, Steps to Reproduce, and Environment details.
  • Automatic formatting of a comprehensive bug report ready for submission to GitHub.
  • GitHub CLI integration to create issues and return the issue URL for user confirmation.

Quick Start

Run the ce-report-bug skill and answer the prompts to submit a GitHub issue.

Frequently Asked Questions about ce-report-bug

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

FAQPage Schema
How do I report a bug for the compound-engineering plugin?▼

To report a bug for the compound-engineering plugin, use a guided questionnaire that captures the bug category, affected component, and reproduction steps, then formats and submits the data as a GitHub issue.

Can I automate GitHub issue creation for plugin troubleshooting?▼

Yes, you can automate GitHub issue creation by collecting environment details and structured bug data, then using GitHub CLI integration to automatically submit the formatted issue and return the URL for confirmation.

What information do I need to submit a structured GitHub bug report?▼

A structured GitHub bug report requires the bug category, affected component, actual versus expected behavior, detailed steps to reproduce, and specific environment details to ensure maintainers can replicate the issue.

Does this bug reporting skill work without additional dependencies?▼

The skill operates without external dependencies, guiding users through capturing environment info and formatting the GitHub issue body directly, relying solely on GitHub CLI integration for final issue submission.

Why does my plugin bug report need environment details and reproduction steps?▼

Environment details and reproduction steps are necessary to provide maintainers with the exact context needed to replicate and diagnose the bug, ensuring the generated GitHub issue contains all required debugging information.

What is the best way to format a bug report for GitHub issues?▼

The best way to format a bug report for GitHub issues is using a guided questionnaire that systematically captures categories, environment data, and reproduction steps into a comprehensive, structured issue body ready for submission.

Related Skills

Explore More Software Engineering Skills→
georgekhananaevgeorgekhananaev
27

github-cli

Wrap GitHub CLI commands with risk classification and confirmation prompts.

Community
Intermediate
dawsonblockdawsonblock

triage-issue

Classify, reproduce, and comment on newly opened GitHub issues.

Community
Intermediate
antithesishqantithesishq
142

antithesis-triage

Extract metadata, diagnose errors, and analyze logs from AI test reports.

Official
Intermediate
DieStokDieStok

ce-report-bug

Collect bug details and create a GitHub issue via the GitHub CLI.

Community
Advanced