bug-report

Create structured bug reports with reproduction steps and severity.

1|Updated May 3, 2026

Search Tags:#code analysis #verification #bug report #software testing #reproduction steps #severity triage #qa workflow

Ready to run

npx skills add https://github.com/imclab/xrA1-swarm --skill bug-report-imclab

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bug-report
Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/bug-report
Command: npx skills add https://github.com/imclab/xrA1-swarm --skill bug-report-imclab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of unstructured, incomplete bug submissions by turning vague reports into consistent, actionable QA artifacts.

Core Features & Use Cases

Structured bug reporting: Produces a complete bug report with summary, severity, priority, environment, reproduction steps, and expected vs actual results.
Codebase analysis: Reads specified files to identify potential bugs such as null references, off-by-one errors, state transition issues, and unhandled edge cases.
Verification workflow: Verifies whether a reported fix actually resolves the bug by re-checking reproduction evidence and relevant tests, then proposes closing or reopening.

Quick Start

Generate a bug report in description mode by providing a clear explanation of what broke, how to reproduce it, and what you expected to happen.

Frequently Asked Questions about bug-report

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

FAQPage Schema

How do I create a structured bug report from a vague issue description?▼

To create a structured bug report, you provide a description of the failure and the system generates an actionable QA artifact enriched with reproduction steps, severity, priority, and expected versus actual results.

Can I analyze source code files to identify potential defects automatically?▼

Yes, you can analyze source code files to identify potential defects like null references, off-by-one errors, and unhandled edge cases by specifying the files for the system to read and evaluate.

How do I verify if a software fix actually resolves a reported bug?▼

You verify a reported fix by re-checking the original reproduction evidence and relevant tests, which allows the system to propose whether to close or reopen the bug record based on the outcome.

What information do I need to provide for effective severity triage in QA workflows?▼

For effective severity triage in QA workflows, you need to provide a clear description of the gameplay or UI issue, explicit reproduction steps, and the environment details to generate a complete and actionable bug report.