bug-report

Standardize bug report creation, analysis, verification, and closure workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of inconsistent, incomplete, or unorganized bug reports that hinder effective debugging and quality assurance in game development.

Core Features & Use Cases

  • Structured Reporting: Generates comprehensive bug reports including severity, priority, reproduction steps, and technical context.
  • Lifecycle Management: Provides dedicated modes for analyzing code for potential bugs, verifying fixes, and formally closing resolved issues.
  • Use Case: When a tester encounters a crash, use this Skill to generate a standardized report that includes the build version, scene state, and reproduction steps, ensuring developers have all the information needed to fix the issue.

Quick Start

Use the bug-report skill to generate a new bug report based on the description of the character clipping issue in the main menu.

Frequently Asked Questions about bug-report

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

FAQPage Schema
How do I standardize bug reporting and lifecycle management in game development?

To standardize bug reporting and lifecycle management, this Skill generates comprehensive reports including severity, priority, reproduction steps, and technical context, while providing automated verification workflows to formally close resolved issues.

How do I generate a structured bug report with reproduction steps and technical context?

You can generate a structured bug report by providing a description of the issue, such as a character clipping error, to automatically document the severity, priority, build version, scene state, and reproduction steps.

Does the bug tracking workflow require codebase search tools and file system write permissions?

Yes, the bug tracking workflow requires integration with codebase search tools to analyze potential bugs and file system write permissions to maintain the bug tracking repository effectively.

What is the best way to verify bug fixes and formally close resolved issues in a software development lifecycle?

The best way to verify bug fixes and close resolved issues is using dedicated lifecycle management modes that enforce systematic tracking, analyze code for potential bugs, and run automated verification workflows before formal closure.

Can I use this automated bug tracking workflow for analyzing code to find potential bugs?

Yes, you can use this automated bug tracking workflow for analyzing code to find potential bugs, as it provides dedicated modes for code analysis and enforces structured documentation throughout the software development lifecycle.