bug-report

Generate structured bug reports from natural-language descriptions and code analysis.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nevesb/idol-agency-maker --skill bug-report-nevesb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-report
Source: https://github.com/nevesb/idol-agency-maker/tree/main/.claude/skills/bug-report
Command: npx skills add https://github.com/nevesb/idol-agency-maker --skill bug-report-nevesb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns informal bug descriptions and raw code observations into consistent, reproducible, and triage-ready bug reports so teams can prioritize and fix issues reliably. It ensures every report includes clear reproduction steps, severity and priority assessments, environment and technical context, and recommended fixes or file references. It also supports verifying fixes and closing bugs with audit records to prevent regressions.

Core Features & Use Cases

  • Structured Reporting: Generates a complete bug report template with summary, ID, severity, environment, reproduction steps, technical context, and related links.
  • Code Analysis Mode: Reads specified files to detect likely defects (null references, off-by-one, race conditions, resource leaks) and produces report records with likely root causes and fixes.
  • Verify & Close Workflows: Verifies fixes by checking files and test results, updates bug status, and appends closure records to production/qa/bugs files after confirmation.
  • Use Case: A QA tester provides a flaky crash description and receives a reproduction-ready bug file and suggested hotfix priorities for the engineering team.

Quick Start

Create a structured bug report from this description: When the player picks up the sword the game crashes on level 3 and the error log shows a null reference.

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 natural language description?

To generate a structured bug report, provide a raw description and the Skill outputs a triage-ready file with summary, severity, reproduction steps, environment context, and related code references. It transforms informal text into verifiable, standardized records for immediate developer debugging.

Can I analyze code to find potential defects like null references and race conditions?

You can analyze code to find potential defects by reading specified files to detect null references, off-by-one errors, race conditions, and resource leaks. The analysis produces report records detailing likely root causes and suggested fixes for the engineering team.

What is the best way to create reproducible steps for a flaky crash in game development?

Creating reproducible steps for a flaky crash involves processing the raw crash description to output full, step-by-step reproduction instructions. The Skill assesses severity and priority while appending technical context and likely affected files identified via Grep or Glob.

Does this bug reporting workflow support verifying fixes and updating bug status?

The bug reporting workflow supports verifying fixes by checking files and test results. After confirmation, it updates bug status and appends closure records to production QA bug files, preventing regressions through auditable verification steps.

How do I triage and assess severity for bugs found during QA testing?

To triage and assess severity during QA testing, the Skill evaluates raw descriptions and code observations to assign priority levels. It outputs a complete template with technical context and recommended fixes, ensuring issues are prioritized and fixed reliably.