Bug

Turn a description of something broken into a GitHub issue of type Bug. Draft the report from what the user gives (plus repo context), show it for approval, and only then file the issue: typed Bug where the repo supports issue types, otherwise labelled bug.

Never open an issue without confirmation, and never invent reproduction steps or facts the user did not provide; mark unknowns as such. Requires git and gh access to the target repository.

Inputs

• A description of the bug (free text, an error/stack trace, or a title plus details)
• The target repository (auto-detected from the current directory's remote)
• Optional: labels, assignee, milestone, or severity the user specifies

When to use

• Filing a clean bug report from a rough description or an error message
• Logging a bug found mid-session without leaving the terminal
• The user says "open a bug", "file this", "create a bug issue", or runs /file-bug

Do not use this to fix the bug, to file feature requests or tasks (different issue type), or to triage existing issues. If the bug is a failing CI check the user wants fixed rather than filed, or the user wants a root cause before filing, do that work instead and come back.