bug

Draft reproducible GitHub bug reports from user-reported breakages.

2|Updated May 13, 2026
One-click install
npx skills add https://github.com/mujtaba3B/gstack-extensions --skill bug-mujtaba3b
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug
Source: https://github.com/mujtaba3B/gstack-extensions/tree/main/pm/skills/bug
Command: npx skills add https://github.com/mujtaba3B/gstack-extensions --skill bug-mujtaba3b

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns reports of broken or unexpected behavior into complete GitHub bug issues with clear reproduction steps, expected versus actual outcomes, and review-ready context.

Core Features & Use Cases

  • Guided bug discovery: Asks targeted questions to capture reproducibility, steps, scope, priority, and ownership without missing critical details.
  • First-party reproduction gate: Verifies the issue before filing, or records an honest blocked or could-not-reproduce outcome when verification is not possible.
  • GitHub-ready issue drafting: Prepares the full ticket body, labels, assignee, and project placement so the bug can be filed accurately and consistently.
  • Use case: A user shares a screenshot of a broken checkout flow, and this Skill gathers the missing details, confirms the failure, and drafts the exact issue for engineering.

Quick Start

Tell me the bug you want filed, and I will help reproduce it, draft the issue, and prepare it for GitHub submission.

Frequently Asked Questions about bug

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

FAQPage Schema
How do I file a reproducible GitHub bug report from a screenshot?

To file a reproducible GitHub bug report from a screenshot, this Skill uses guided discovery to extract step-by-step reproduction details, verifies the breakage, and drafts the complete issue with labels and assignees.

What is the best way to document expected versus actual outcomes for issue filing?

Documenting expected versus actual outcomes requires capturing the broken behavior and contrasting it with the correct system response, which this Skill structures automatically into a review-ready GitHub issue body.

How does QA coordination work when reporting unexpected UI errors?

QA coordination for unexpected UI errors works by asking targeted questions to establish scope and priority, followed by a first-party reproduction gate to verify the failure before creating the GitHub ticket.

Can I use this to file GitHub issues if I cannot reproduce the bug?

Yes, you can file GitHub issues even when you cannot reproduce the bug, because the Skill records an explicit waiver or an honest blocked outcome when first-party verification is not possible.

Does this bug reporting tool configure project placement for filed GitHub issues?

Yes, this bug reporting tool configures project placement for filed GitHub issues, simultaneously preparing the full ticket body, labels, assignees, and project board assignment during the drafting process.

What are the limitations of automated triage for user-reported breakages?

Automated triage for user-reported breakages is limited by its dependency on guided discovery, meaning it requires clear reproduction steps or an explicit waiver when first-party verification fails to document the issue accurately.