skills.rest
LeKay
LeKayCOMMUNITY
Explore all skills by this author →
GitHub

bug-report

Create, analyze, verify, and close Markdown bug reports with Python code analysis.

Updated May 24, 2026
Search Tags:#code analysis#bug fixing#QA#issue tracking#bug reporting
One-click install
npx skills add https://github.com/LeKay/ai-game --skill bug-report-lekay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-report
Source: https://github.com/LeKay/ai-game/tree/main/.claude/skills/bug-report
Command: npx skills add https://github.com/LeKay/ai-game --skill bug-report-lekay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating and verifying bug reports, ensuring that every report includes essential information and context for effective issue tracking.

Core Features & Use Cases

  • Structured Bug Reports: Automatically generates bug reports with predefined sections for summary, classification, environment, reproduction steps, technical context, evidence, and related issues.
  • Code Analysis: Analyzes source code to identify potential bugs, providing suggestions for fixes.
  • Verification and Closure: Allows for verification of bug fixes and closure of reports, ensuring that resolved issues are properly documented.
  • Use Case: Quickly generate a bug report from a description or analyze a piece of code to identify potential issues, then verify the fix and close the report.

Quick Start

Create a bug report from a description by running 'bug-report [description]' or analyze a code file for potential bugs with 'bug-report analyze [path-to-file]'.

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 code analysis?▼

To automate bug reporting, provide a text description or file path to the bug-report command. It analyzes your codebase using shell commands and Python, then outputs a Markdown report with reproduction steps, environment details, and technical context.

What is the best way to document reproduction steps for issue tracking?▼

The best way to document reproduction steps is using a structured bug report. This Skill automatically formats reports with predefined sections for summary, classification, environment, evidence, and related issues to ensure effective issue tracking.

Can I analyze source code for potential bugs using bash and grep?▼

Yes, you can analyze source code for potential bugs using bash and grep. This Skill integrates with your codebase by executing shell commands and Python scripts to identify issues and suggest fixes within the generated report.

How do I verify a bug fix and close a bug report?▼

To verify a bug fix and close a bug report, use the verification and closure feature. This ensures resolved issues are properly documented and the report is closed after confirming the fix within your software development QA process.

Do I need Markdown to format bug reports for QA processes?▼

Yes, Markdown is utilized for bug report formatting in QA processes. The Skill generates reports in Markdown, organizing details like classification, technical context, and evidence into structured sections for effective issue tracking.

What technical context should be included when creating a bug report?▼

When creating a bug report, the technical context should include source code analysis, environment details, reproduction steps, evidence, and related issues. This Skill ensures all essential information is automatically captured and structured.

Related Skills

Explore More Software Engineering Skills→
tomguntomgun

writing-tests

Write and run unit, integration, and acceptance tests for code changes.

Community
Intermediate
rcrathrcrath
1

wayq-regress

Monitor GitHub issues for regressions and report findings in audio format.

Community
Intermediate
Donaldshen27Donaldshen27

test-driven-development

Enforce a red-green-refactor workflow by writing failing tests before code.

Community
Advanced
BrennonTWilliamsBrennonTWilliams
7

ll-refine-issue

Refine software issue documentation via codebase research and gap analysis.

Community
Intermediate