skills.rest
nuoyanruoshui
nuoyanruoshuiCOMMUNITY
Explore all skills by this author →
GitHub

bug-report

Generate structured bug reports from issue descriptions or code analysis findings.

47|12|Updated Jun 14, 2026
Search Tags:#code analysis#qa#issue tracking#regression testing#bug reporting#reproduction steps#fix verification
One-click install
npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill bug-report-nuoyanruoshui
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-report
Source: https://github.com/nuoyanruoshui/GodotGameFramework/tree/main/Godot/.claude/skills/bug-report
Command: npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill bug-report-nuoyanruoshui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns vague bug descriptions and code findings into actionable, traceable reports with consistent reproduction steps, severity, technical context, and lifecycle status.

Core Features & Use Cases

  • Description-Based Reporting: Convert a user's issue description into a complete bug report with classification, environment, reproduction steps, expected results, and evidence.
  • Code Analysis: Inspect specified files for null references, edge cases, state-transition errors, resource leaks, and other potential defects.
  • Verification and Closure: Check whether reported fixes resolve bugs, review related tests and regressions, and record verified closure details only after confirmation.
  • Use Case: Give the Skill a gameplay issue description to produce a report, save it under the project's QA bug directory, and then verify and close it after the fix is implemented.

Quick Start

Use the bug-report skill to analyze the specified source file and generate structured reports for every potential bug it contains.

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 vague issue description?▼

To generate a structured bug report, provide the issue description to trigger analysis that produces classification, environment details, reproduction steps, expected results, and evidence for traceable QA tracking.

Can I analyze source code to detect potential defects like null references and resource leaks?▼

Yes, you can analyze source code to detect potential defects including null references, edge cases, state-transition errors, and resource leaks, which are then compiled into structured bug reports.

How do I verify a bug fix and check for regressions before closing the issue?▼

Bug fix verification involves checking whether the reported fix resolves the issue, reviewing related tests for regressions, and recording verified closure details only after explicit user confirmation.

What is the best way to track bug severity and lifecycle status during software quality workflows?▼

Tracking bug severity and lifecycle status involves generating structured reports with consistent classification, technical context, and controlled closure records to maintain actionable software quality workflows.

Does bug reporting require repository search and file-reading capabilities?▼

Yes, generating and updating bug reports requires repository search and file-reading capabilities to inspect code, plus explicit user confirmation before writing or updating any bug records.

Related Skills

Explore More Software Engineering Skills→
kay6198835kay6198835

bug-report

Convert user descriptions into structured bug reports with reproduction steps.

Community
Advanced
ScivorScivor

qa

Automate web application testing and verify fixes across iterative cycles.

Community
Advanced
pixel-cellarpixel-cellar
277

bug-report

Generate structured Markdown bug reports with reproduction steps and severity assessment.

Official
Intermediate
robertphyattrobertphyatt
7

testing-theatre-detection

Detect missing assertions, excessive mocking, and swallowed errors in JavaScript and Python test suites.

Community
Advanced