skills.rest
DieStok
DieStokCOMMUNITY
Explore all skills by this author →
GitHub

ce-report-bug

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

Updated Apr 26, 2026
Search Tags:#automation#workflow#github#plugin#issue#report#bug
One-click install
npx skills add https://github.com/DieStok/ridder_lab_retreat_ai_hackathon_2026 --skill ce-report-bug-diestok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce-report-bug
Source: https://github.com/DieStok/ridder_lab_retreat_ai_hackathon_2026/tree/main/.agents/skills/compound-engineering/skills/ce-report-bug
Command: npx skills add https://github.com/DieStok/ridder_lab_retreat_ai_hackathon_2026 --skill ce-report-bug-diestok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gather and structure bug details for the compound-engineering plugin, then automatically file a GitHub issue with a consistent report.

Core Features & Use Cases

  • Guided questioning to categorize the bug, identify the affected component, capture reproduction steps, and collect environment details.
  • Automatic formatting of a structured bug report suitable for maintainers, including steps, errors, and expected behavior.
  • One-click submission via the GitHub CLI with clear success feedback and a created issue URL.

Quick Start

Open the bug-reporting tool for the compound-engineering plugin and follow the prompts to collect details and file 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 automatically report a bug to GitHub from a plugin?▼

You can automatically report a bug to GitHub by answering guided questions for category, component, reproduction steps, and environment, which the tool formats into a structured issue and submits via the GitHub CLI, returning the issue URL.

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

A structured bug report for a GitHub issue requires capturing the category, affected component, reproduction steps, environment details, errors, and expected behavior to provide maintainers with consistent, actionable context.

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

Yes, you need the GitHub CLI installed to automate issue creation, as the tool uses it to submit the formatted bug report; if the CLI is unavailable, the tool provides fallback prompts instead of submitting.

What details do I need to provide when filing a bug report for a plugin?▼

When filing a bug report for a plugin, you need to provide the bug category, affected component, step-by-step reproduction instructions, environment details, encountered errors, and the expected behavior.

What happens if GitHub tooling is unavailable during bug report submission?▼

If GitHub tooling is unavailable during bug report submission, the automated issue creation fails gracefully and the tool provides fallback prompts to ensure you still capture the structured bug details.

Related Skills

Explore More Software Engineering Skills→
dantasgutdantasgut

speckit-git-remote

Extract the Git remote URL and parse owner and repository name.

Community
Basic
qauth-labsqauth-labs
23

investigate-issue

Collect GitHub issue details, comments, related issues, and pull requests.

Official
Basic
RsultCodingRsultCoding

replicate-issue

Replicate GitHub issues by testing symptoms with browser automation.

Community
Advanced
systeminitsysteminit
530

swamp-issue

Create labeled GitHub issues for the Swamp CLI tool via GitHub CLI.

Official
Basic