bug-report

Generate structured bug reports from descriptions and code analyses.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/packetalien/cursor-game-studios --skill bug-report-packetalien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-report
Source: https://github.com/packetalien/cursor-game-studios/tree/main/.cursor/skills/bug-report
Command: npx skills add https://github.com/packetalien/cursor-game-studios --skill bug-report-packetalien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool automatically converts user bug descriptions or code findings into a complete, standardized bug report, including reproduction steps, severity, and context.

Core Features & Use Cases

  • Description to report: Generate a fully structured Bug Report from a narrative or issue summary.
  • Code analysis integration: Inspect code paths to populate likely failure points and affected modules.
  • Lifecycle support: Create, verify, and close reports following QA and development workflows.

Quick Start

Describe a bug scenario and run bug-report to generate a ready-to-file 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 standardized bug report from a narrative description?

To create a standardized bug report, provide a narrative description or issue summary. The tool automatically structures it into a ready-to-file document with reproduction steps, severity, and context.

Can I generate bug reports directly from code analysis findings?

Yes, you can generate bug reports from code analysis findings. The tool inspects code paths to populate likely failure points and affected modules directly into the structured documentation.

What is the best way to enforce a consistent bug template across QA workflows?

The best way to enforce a consistent bug template is using an automated reporting tool. It captures reproduction steps, severity, context, and artifact linkage, ensuring traceable documentation for QA and development.

Does this bug reporting approach support the full incident response lifecycle?

Yes, this bug reporting approach supports the incident response lifecycle. You can create, verify, and close reports following standardized QA and development workflows.

How to capture reproduction steps and severity for incident documentation?

To capture reproduction steps and severity, describe the bug scenario and run the automated generation process. It extracts the necessary context and applies it to a standardized template for traceable incident documentation.