bug-report

Generate structured bug reports with reproduction steps and severity.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/LordKuper/agentic-game-studio --skill bug-report-lordkuper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-report
Source: https://github.com/LordKuper/agentic-game-studio/tree/main/.claude/skills/bug-report
Command: npx skills add https://github.com/LordKuper/agentic-game-studio --skill bug-report-lordkuper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a structured bug report from a description, or analyzes code to identify potential bugs. Ensures every bug report has full reproduction steps, severity assessment, and context.

Core Features & Use Cases

  • Description Mode: Generate a complete bug report from a natural language description.
  • Analyze Mode: Inspect target code to identify potential bugs and surface likely failure points.
  • Verification & Closure: Provide verification-ready status updates and closure notes for resolved issues.

Quick Start

Provide a concise bug description to generate a complete, structured bug report.

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 natural language description?

To create a structured bug report, provide a concise description of the issue. The system generates a standardized template enforcing reproduction steps, severity assessment, and environment context for consistent documentation across files and modules.

Can I analyze code to identify potential bugs and failure points?

Yes, you can analyze code to identify potential bugs by inspecting the target code. This process surfaces likely failure points and transforms scattered reports into structured documentation for triage workflows.

What is the standardized template for bug reproduction steps and severity?

The standardized template for bug reproduction enforces consistent documentation by requiring reproduction steps, severity assessment, environment details, status, and lifecycle actions including Description, Analyze, Verify, and Close.

How do I verify and close resolved bugs in a triage workflow?

To verify and close resolved bugs in a triage workflow, the system provides verification-ready status updates and closure notes. It guides triage decisions by validating input and enforcing lifecycle actions like Verify and Close.

Do I need specific dependencies to generate bug reports across files and modules?

No specific dependencies are required to generate bug reports across files and modules. The system operates independently to transform scattered user descriptions into consistent documentation with reproduction steps and severity.