skills.rest
MichaelSolati
MichaelSolatiCOMMUNITY
Explore all skills by this author →
Website𝕏@MichaelSolatiGitHub

bug-report

Generate standardized bug reports with reproduction steps and severity classification.

Updated Jul 22, 2025
Search Tags:#game development#code analysis#qa#bug reporting#bug verification#defect tracking#bug lifecycle
One-click install
npx skills add https://github.com/MichaelSolati/mkai --skill bug-report-michaelsolati
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-report
Source: https://github.com/MichaelSolati/mkai/tree/main/profiles/game-dev/skills/bug-report
Command: npx skills add https://github.com/MichaelSolati/mkai --skill bug-report-michaelsolati

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Game development teams often face inconsistent, incomplete bug reports that delay debugging, make fix verification difficult, and lead to unresolved issues impacting player experience.

Core Features & Use Cases

  • Structured Bug Report Generation: Create standardized bug reports from user descriptions or static code analysis, with full reproduction steps, severity assessment, and context.
  • Fix Verification: Confirm that implemented fixes actually resolve reported bugs by re-running reproduction steps and checking for regressions.
  • Bug Lifecycle Management: Formally close verified bugs with closure records and update triage reports to keep tracking accurate. Use Case: A QA tester can describe a player-reported inventory glitch to get a complete bug report, or a developer can analyze a new game script to catch potential crashes before release.

Quick Start

Use the bug-report skill to generate a structured bug report for the player movement stutter issue observed in the latest playtest session.

Frequently Asked Questions about bug-report

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

FAQPage Schema
How do I generate a standardized game bug report from a player description?▼

Generating a standardized game bug report involves parsing user descriptions to produce actionable documentation with full reproduction steps, severity classification, and context to eliminate incomplete defect reporting.

What is static code analysis for identifying potential game defects?▼

Static code analysis for game defects is the process of examining new game scripts to catch potential crashes and identify code-level issues before release, creating structured bug reports to track these resolved problems.

How do I verify implemented game bug fixes and check for regressions?▼

Verifying implemented game bug fixes requires re-running the original reproduction steps to confirm the defect is resolved, checking for regressions, and formally closing the issue with a verified closure record.

Can I use this for end-to-end bug lifecycle tracking in game QA workflows?▼

Yes, this supports end-to-end bug lifecycle tracking for game QA workflows by managing formal bug closure records and updating triage reports to keep defect tracking accurate from creation to resolution.

Why does inconsistent bug documentation delay game debugging?▼

Inconsistent bug documentation delays game debugging because incomplete reports lack reproducible steps and severity context, making fix verification difficult and leading to unresolved issues that impact player experience.

Related Skills

Explore More Software Engineering Skills→
PuckAPIPuckAPI
2

feature-engineering

Convert raw hockey data into model-ready features with lagging and rolling windows.

Official
Intermediate
SignmanalSignmanal
1

github-issues

Manage GitHub issue lifecycles via gh CLI or REST API.

Community
Intermediate
puwenjunluck-pixelpuwenjunluck-pixel

fix

Automate bug fixing with root cause analysis and regression testing.

Community
Advanced
cegit27cegit27
3

canary

Monitor live production apps for console errors and performance regressions.

Official
Advanced