mirror of
https://github.com/shipshitdev/skills.git
synced 2026-09-19 06:04:15 +08:00
Vincent
9365897938
* refactor!: unify GitHub identities and provider-aware board workflows * fix: resolve renamed helpers from their installed packages * fix: validate published names and preserve transport types
1.5 KiB
1.5 KiB
Bug - File a GitHub Bug Issue
Turn a description of something broken into a GitHub issue of type Bug.
Drafts a structured report, previews it, and files it only after you confirm —
typed Bug where the repo supports issue types, otherwise labelled bug.
Usage
/bug <description> # draft a bug report from the description, preview, then file (default)
/bug # draft from the current context / recent error, preview, then file
/bug draft <desc> # draft and print the report only — create nothing
Workflow
Use the bug skill.
- Detect the repo (from the current remote) and whether it supports a
Bugissue type or needs thebuglabel fallback. Stop if issues are disabled. - Draft a structured report — title, summary, steps to reproduce, expected vs actual, environment. Unknowns are marked, never invented. Pasted errors/stack traces are quoted verbatim.
- Print the drafted issue and wait for explicit confirmation.
- Create the issue with
--type Bug(or--label bugfallback), applying only the labels/assignee/milestone you named, and return the issue URL.
Gates
- Never open the issue without explicit confirmation.
- Never fabricate reproduction steps, versions, or behavior — mark gaps as not provided.
- Files bugs only; for feature requests or tasks, use the matching issue type.
- To root-cause before filing, use
debug— it escalates tosystematic-debuggingitself once a fix attempt has failed; for a failing CI check, usegithub-fix-ci.