bug-report

Generate structured bug reports with steps, severity, and context.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams convert user reports and code observations into precise, reproducible bug reports with structured fields and evidence.

Core Features & Use Cases

  • Automatic template-based bug report generation from plain descriptions.
  • Analyze code paths to surface likely failures and reproduction steps.
  • Phase-based workflow including describe, analyze, verify and close for end-to-end QA.

Quick Start

Describe an issue in detail to generate a complete Bug Report with steps, severity, and context.

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 structured bug report from a plain text issue description?

To generate a structured bug report, you input a plain text issue description and the tool applies an automatic template to produce a complete report with reproducible steps, severity, and context. It converts raw observations into precise, structured fields for issue triage.

What is the best way to analyze code paths to find reproduction steps for a bug?

Analyzing code paths to find reproduction steps involves tracing execution flow to surface likely failures. This skill examines code observations to automatically generate actionable reproduction steps, identifying where and why a failure occurs within the logic.

Can I use a phase-based workflow for QA triage and issue verification?

Yes, you can use a phase-based workflow for QA triage and issue verification through describe, analyze, verify, and close phases. This end-to-end process supports complete issue reproduction, evidence collection, and vendor-sourcing before closing.

How do I convert user reports into precise bug reports with evidence collection?

To convert user reports into precise bug reports with evidence collection, you process the raw descriptions through an automated template. The workflow extracts context, adds evidence, and structures the data for immediate use in QA workflows and code reviews.

Does this bug reporting tool require any specific dependencies or environments?

No, this bug reporting tool does not require any specific dependencies or environments to function. It operates independently to generate structured reports from descriptions and code observations without needing external components.