Create structured GitHub bug tickets from Given/When/Then inputs.
npx skills add https://github.com/me2resh/apexyard --skill bug-me2resh
Please help me install this Agent Skill. Skill: bug Source: https://github.com/me2resh/apexyard/tree/main/.claude/skills/bug Command: npx skills add https://github.com/me2resh/apexyard --skill bug-me2resh
This Skill eliminates the back-and-forth of vague bug reports by converting a raw description into a structured GitHub issue that includes scenario, repro steps, severity, and optional context.
Create a bug issue for the repository by describing the bug scenario, repro steps, and severity after you run: /bug Profile picture upload fails.
High-intent search queries and answers about installing and using this skill.
To create structured GitHub issues, this tool converts raw bug descriptions into formatted tickets using Given/When/Then scenarios, repro steps, and severity levels. It validates the target repository and displays the fully formatted issue for approval before running gh issue create with appropriate labels.
The Given When Then format for bug ticket templating structures defect reports by forcing a consistent narrative: starting state, trigger, unexpected result, and expected behavior. This structure eliminates vague bug reports and ensures clear reproduction steps.
To add severity and priority labels to GitHub bug reports, the tool collects concrete reproduction steps and assigns a P0, P1, or P2 priority level during the ticket creation workflow. These severity selections are applied automatically when running gh issue create.
Yes, you can file GitHub issues across a multi-project repository layout using a single template. The tool resolves the correct target repository during the formatting process and confirms the fully formatted issue before creating it.
Yes, the bug reporting workflow uses a confirmation-first approach that shows the fully formatted GitHub issue for your approval before creating it. This ensures the Given/When/Then scenario, repro steps, and severity are correct before executing gh issue create.
The best way to report UI and environment-specific defects is converting them into structured tickets with Given/When/Then scenarios and repro steps. This approach applies to reporting workflow defects and ensures environment-specific details are captured before running gh issue create.
zoraxlCreate structured GitHub issues for bug tracking in multi-repository environments.
learnzdevelopmenthubCreate GitHub pull requests and poll CI status for feature branches.
eysenfalkManage GitHub projects with AI swarm coordination for issue tracking and sprint planning.
CENKSSSCreate structured bug reports with severity assessment and automated triage.
