bug-report

Generate structured bug reports and verify fixes in codebases.

Updated May 16, 2026
One-click install
npx skills add https://github.com/SeongHuni/LightNShadowSurviver --skill bug-report-seonghuni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-report
Source: https://github.com/SeongHuni/LightNShadowSurviver/tree/main/GameStudio/codex/skills/bug-report
Command: npx skills add https://github.com/SeongHuni/LightNShadowSurviver --skill bug-report-seonghuni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the process of creating and verifying bug reports, ensuring all necessary information is captured and easily accessible.

Core Features & Use Cases

  • Structured Bug Reporting: Generates a detailed bug report with all required information.
  • Code Analysis: Identifies potential bugs in code files.
  • Bug Verification: Confirms whether a reported fix resolved the issue.
  • Bug Closure: Marks a bug as closed after verification.
  • Use Case: When a developer encounters a bug in the code, they can use this Skill to generate a report, analyze the code, verify the fix, and close the bug.

Quick Start

Generate a bug report for an issue described in the text 'The game crashes when the player attempts to jump.'

Frequently Asked Questions about bug-report

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

FAQPage Schema
How do I create structured bug reports from code analysis?

Structured bug reports are generated by analyzing codebase files to identify potential bugs and capturing all required issue details in a standardized template. This ensures necessary information is accessible for resolving software development problems.

Can I automate bug verification after applying a code fix?

Yes, bug verification is automated by executing scripts against the codebase to confirm whether a reported fix successfully resolved the identified issue. This process validates the fix before marking the bug as closed.

What is the best way to track issue resolution in a software development workflow?

Tracking issue resolution is best handled by generating a detailed bug report, analyzing the code, verifying the fix, and formally closing the bug. This structured approach ensures issues are fully resolved and documented.

Do I need codebase access to identify and report potential bugs?

Yes, codebase access is required to identify potential bugs in code files and generate a structured bug report. The Skill executes scripts within the software development environment to analyze and verify issues.

How does code analysis help with bug reporting and closure?

Code analysis helps bug reporting by identifying potential defects within code files and capturing them in a structured format. After verification scripts confirm the fix, the bug is marked as closed, completing the workflow.