bug-report

Generate structured bug reports from user descriptions or static code analysis.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/johnatas-henrique/overdrive --skill bug-report-johnatas-henrique
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-report
Source: https://github.com/johnatas-henrique/overdrive/tree/main/.opencode/skills/bug-report
Command: npx skills add https://github.com/johnatas-henrique/overdrive --skill bug-report-johnatas-henrique

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unstructured, incomplete bug reports waste development and QA time by missing critical context like exact reproduction steps, severity ratings, and affected systems, leading to delayed fixes and misprioritized issues that impact game quality.

Core Features & Use Cases

  • Structured Bug Report Generation: Create standardized bug reports from user descriptions with all required fields including severity, priority, reproduction steps, and technical context.
  • Static Code Analysis: Scan game code files to identify potential bugs like null references, off-by-one errors, unhandled edge cases, and resource leaks before they reach players.
  • Fix Verification & Closure: Verify that reported bug fixes actually resolve the issue by re-running reproduction steps and checking for regressions, then formally close bugs with closure records.
  • Use Case: A QA tester can use this skill to turn a vague user report of "the car crashes when turning left on track 3" into a full bug report with exact steps to reproduce, S2 severity rating, and list of affected game systems, or a developer can run it on a new game mode script to catch potential bugs before release.

Quick Start

Share a description of the bug you encountered, or provide the path to a code file you want to scan for potential issues, to generate a structured bug report or code analysis.

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 user description?

To create a structured bug report from a vague user description, provide the raw text to generate a standardized filing with exact reproduction steps, severity and priority classification, and technical context. This eliminates incomplete bug reports that delay development workflows.

What is the best way to verify bug fixes and check for regressions in game QA testing?

The best way to verify bug fixes in game QA testing is to re-run the exact reproduction steps from the original report and check for regressions. This confirms the issue is resolved and allows you to formally close bugs with formal closure records.

How do I classify severity and priority for gameplay and crash bugs?

You classify severity and priority for gameplay and crash bugs by applying standardized rating scales during the report generation process. This ensures defects are accurately categorized and misprioritized issues impacting game quality are avoided.

Can I use this for reporting UI and audio visual bugs in game development?

Yes, you can use this for reporting UI, audio, visual, performance, and crash bugs in game development. It applies to game quality assurance workflows by generating full reproduction step documentation and gathering technical context for each specific defect type.