file-bug-issue

Create a reproducible GitHub issue with reproduction steps and environment details.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/daodaoedu/daodao --skill file-bug-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-bug-issue
Source: https://github.com/daodaoedu/daodao/tree/main/.claude/skills/file-bug-issue
Command: npx skills add https://github.com/daodaoedu/daodao --skill file-bug-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill converts user-reported bugs into traceable GitHub issues by collecting reproduction steps, context, and environment details, enabling faster triage and resolution.

Core Features & Use Cases

  • Structured bug reporting: captures error phenomena, reproduction steps, attempted fixes, related files, and environment data.
  • Repo-scoped issue creation: validates target repository and labels, drafts a detailed issue description, and creates the issue via GitHub CLI.
  • Use Case: when a bug is found during a project discussion, generate a replicable issue that includes steps to reproduce and debugging notes for the assignee.

Quick Start

Provide the bug details and target repository to automatically file a GitHub issue with reproduction steps.

Frequently Asked Questions about file-bug-issue

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

FAQPage Schema
How do I create a reproducible GitHub issue from a bug discussion?

To create a reproducible GitHub issue, you can collect error context, reproduction steps, and environment details into a structured draft and post it via the GitHub CLI after user confirmation. This ensures the bug report is actionable and traceable for triage.

What is the best way to automate bug reporting into GitHub issues?

Automating bug reporting into GitHub issues involves capturing structured inputs like error phenomena, attempted fixes, and related files to draft a detailed description. The workflow validates repository access and applies labels before creating the issue automatically.

Do I need to specify a target repository to file a bug issue?

Yes, you need to specify a target repository to file a bug issue. The skill validates your repository access and checks available labels for that specific repo before drafting and posting the issue via the GitHub CLI.

What details should I include when reporting a bug for faster triage?

For faster triage, you should include error phenomena, step-by-step reproduction instructions, attempted fixes, related files, and environment data. This structured context transforms a vague bug report into a replicable issue with debugging notes for the assignee.

Can I review the GitHub issue draft before it is actually posted?

Yes, you can review the GitHub issue draft before it is posted. The workflow prepares a detailed issue description with labels and environment details, requiring your explicit confirmation before executing the GitHub CLI command to create the issue.

How does validating repository access work when creating GitHub issues?

Validating repository access works by checking your permissions against the specified target repository before drafting the issue. This ensures you have the necessary access rights to apply labels and successfully create the issue via the GitHub CLI without encountering authorization errors.