bug

Create structured GitHub bug reports with Given/When/Then scenarios.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/AAbdulghany/fms --skill bug-aabdulghany
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug
Source: https://github.com/AAbdulghany/fms/tree/main/.claude/skills/bug
Command: npx skills add https://github.com/AAbdulghany/fms --skill bug-aabdulghany

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating and standardizing bug reports is error-prone and inconsistent across teams. This skill automates the generation of well-formed GitHub issues by enforcing a Given/When/Then structure, including repro steps and severity, so payloads are clear and actionable.

Core Features & Use Cases

  • Creates a structured GitHub Issue for bugs with a clear Given/When/Then scenario, repro steps, environment, and severity.
  • Asks guided questions, formats the ticket for confirmation, and then creates the issue to ensure accuracy and traceability.
  • Supports adopter-specific templates and safe creation flows via integrated portfolio helpers and path resolution.

Quick Start

Describe a bug succinctly and let the tool guide you through generating a structured GitHub issue.

Frequently Asked Questions about bug

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

FAQPage Schema
How do I automatically create structured GitHub issues from bug reports?

You can automatically create structured GitHub issues by using a guided tool that enforces Given/When/Then scenarios, repro steps, environment details, and severity. This ensures your bug reports are consistently formatted, clear, and actionable before the issue is created.

What is the best way to standardize bug ticket formatting across a development team?

Standardizing bug ticket formatting is best achieved by automating the creation of GitHub issues with a enforced structure. Using guided questions to capture Given/When/Then scenarios, repro steps, and severity ensures consistent, error-free reporting across teams.

Can I use Given/When/Then scenarios when logging bugs on GitHub?

Yes, you can log bugs using Given/When/Then scenarios by leveraging an automated issue creation tool. It guides you through defining the scenario, repro steps, environment, and severity, then formats the payload into a well-formed GitHub issue.

How do I ensure accuracy before a bug ticket is created on GitHub?

To ensure accuracy before a bug ticket is created, you can use a safe creation flow that formats the ticket for confirmation. This guided process asks structured questions about repro steps and severity, allowing you to review the payload before final creation.

Does this bug reporting approach support custom issue templates?

Yes, this bug reporting approach supports custom issue templates. It integrates with template resolvers and portfolio helpers to support adopter-specific customization, allowing you to tailor the structured Given/When/Then bug reports to your workflow.

Why should I automate bug tracking instead of manually writing GitHub issues?

You should automate bug tracking because manually creating and standardizing bug reports is error-prone and inconsistent. Automation enforces a clear Given/When/Then structure, including repro steps and severity, so your GitHub issues are consistently formatted and actionable.