bug-report

Generate structured bug reports from descriptions, code analysis, or QA verification.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/scomofo/dragon-forge --skill bug-report-scomofo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-report
Source: https://github.com/scomofo/dragon-forge/tree/main/.agents/skills/bug-report
Command: npx skills add https://github.com/scomofo/dragon-forge --skill bug-report-scomofo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns vague bug descriptions or code observations into structured, reproducible bug reports that teams can triage and fix quickly, with clear severity, environment, and evidence.

Core Features & Use Cases

  • Description Mode: Converts a user's bug description into a complete bug report including classification, reproduction steps, expected vs actual results, and technical context.
  • Analyze Mode: Reads specified file(s) and proposes likely bugs such as null references, off-by-one errors, race conditions, unhandled edge cases, and incorrect state transitions.
  • Verify/Close Workflows: Reads the recorded QA bug file, checks whether the issue still reproduces, and supports marking it verified fixed and closing with a resolution record.

Quick Start

Use bug-report in description mode to generate a full report from a bug description by saying: bug-report "I think the hatchery dragon unlock duplicates shiny upgrade XP when clicking unlock twice; it happens after saving and reloading; expected is single XP grant; actual is double XP and duplicate shiny upgrade."

Frequently Asked Questions about bug-report

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

FAQPage Schema
How do I write a structured bug report with clear reproduction steps and severity?

To write a structured bug report, convert vague descriptions into actionable formats by defining classification, environment, reproduction steps, expected versus actual results, and technical context to generate prioritized severity fields for rapid triage.

How do I analyze source code to find race conditions and incorrect state transitions?

You can analyze source code to find race conditions and incorrect state transitions by reading specified files to propose likely bugs, targeting issues like null references, off-by-one errors, and unhandled edge cases for technical context extraction.

What is the best way to verify and close a bug after QA testing?

The best way to verify and close a bug after QA testing is to read the recorded bug file, check whether the issue still reproduces, and mark it verified with a gated closure update and resolution record sent to production and QA.

Can I generate actionable bug reports for gameplay crashes and UI performance issues?

Yes, you can generate actionable bug reports for gameplay crashes and UI performance issues by searching related files for context and producing complete reports with evidence placeholders and environment specifications across multiple workflows.

Does automated bug report generation work without adding dependencies?

Automated bug report generation works without adding dependencies, using internal workflows to search related files for context and transform user descriptions into structured reports with gated verification and closure updates.