bug-report

Create formatted GitHub bug report issues via the gh CLI.

1|Updated Oct 27, 2025

Search Tags:#automation #workflow #github #issues #sop #bug-report

Ready to run

npx skills add https://github.com/AEtherlight-ai/lumina --skill bug-report

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bug-report
Source: https://github.com/AEtherlight-ai/lumina/tree/main/.claude/skills/bug-report
Command: npx skills add https://github.com/AEtherlight-ai/lumina --skill bug-report

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh.

What problem does it solve?

This Skill automates the creation of properly formatted GitHub bug report issues that follow ÆtherLight's SOP, reducing back-and-forth and ensuring consistent reporting.

Core Features & Use Cases

Structured Issue Creation: Generates a complete bug report with description, steps, environment, and context.
Duplicate Detection: Checks for existing bugs before creating a new issue to avoid duplicates.
Severity & Component Guidance: Classifies severity and associates the report with an affected component.

Quick Start

Use the bug-report skill to create an issue on AEtherLight's lumina repo by providing a brief description. Example: /bug-report --description="Login fails under OAuth after update" --severity=high --component="auth"

Frequently Asked Questions about bug-report

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

FAQPage Schema

How do I automate GitHub bug report creation with consistent formatting?▼

Automate GitHub bug report creation by using a workflow that enforces SOP-compliant formatting, including structured fields for description, reproduction steps, environment details, and severity classification. The bug-report skill applies this automation via the gh CLI, ensuring every report includes required information and proper labeling before submission.

How do I check for duplicate bug reports before creating a new issue?▼

Duplicate detection is built into the bug-report workflow—it searches existing GitHub issues before creating a new one, preventing redundant reports. This avoids wasted effort and keeps issue tracking organized by surfacing related problems already filed.

Can I classify bug severity and assign components automatically when filing issues?▼

Yes. The bug-report skill accepts severity and component parameters during issue creation, automatically applying the correct labels and categorization to your GitHub issue. This ensures proper triage and routing without manual post-creation edits.

What information does a properly formatted bug report require?▼

A properly formatted bug report requires a concise title, description of the problem, step-by-step reproduction instructions, environment details (OS, version, relevant context), and severity classification. The bug-report skill prompts for each field and structures them before submission to GitHub.

Do I need GitHub CLI installed to create bug reports this way?▼

Yes, the gh CLI is a required dependency for the bug-report skill. It handles authentication and command execution to submit formatted issues directly to GitHub without manual web interface steps.

What happens if GitHub authentication fails or the issue submission encounters an error?▼

The bug-report skill includes robust error handling for authentication and command execution failures. It catches and reports these errors clearly so you can resolve credential issues or network problems before retrying submission.