bug-report

Name: bug-report
Availability: InStock
Author: carlosq96

Generate structured markdown bug reports from user descriptions.

Updated Apr 9, 2026

Search Tags:#automation #qa #verification #analysis #report #bug

Ready to run

npx skills add https://github.com/CarlosQ96/robot-crawler --skill bug-report-carlosq96

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bug-report
Source: https://github.com/CarlosQ96/robot-crawler/tree/main/.agents/skills/bug-report
Command: npx skills add https://github.com/CarlosQ96/robot-crawler --skill bug-report-carlosq96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many teams struggle to create consistent, detailed bug reports that include reproduction steps, severity assessments, and contextual information, leading to slower triage and resolution.

Core Features & Use Cases

Structured Bug Report Generation: Converts a plain‑text description into a comprehensive markdown report with all required fields.
Code Analysis Mode: Scans specified source files to automatically detect potential bugs and produce ready‑to‑file reports.
Verification & Closure Workflow: Reads existing QA bug files, re‑runs reproduction steps, updates status, and records closure details.

Quick Start

Ask bug-report to generate a full bug report for the issue: the player character falls through the floor in level 3.

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

To generate a structured bug report, provide a plain-text description of the issue. The tool converts it into a comprehensive markdown report with reproduction steps, severity assessment, and contextual information.

Can I scan source files to automatically detect and document code issues?▼

Yes, you can scan source files to automatically detect potential bugs. The code analysis mode examines specified files and produces ready-to-file bug reports based on its findings.

What is the best way to verify and close existing bug reports in a QA directory?▼

The best way to verify and close existing bug reports is to read the markdown files in your QA directory, re-run the reproduction steps, update the status, and record closure details automatically.

Does bug report generation require access to the codebase?▼

Yes, generating comprehensive bug reports requires codebase access for file searching and optional analysis of source files to ensure accurate reproduction steps and contextual documentation.

Why use markdown for software bug documentation instead of plain text?▼

Markdown provides a structured format for bug documentation, ensuring consistent fields for severity assessment and reproduction steps, which accelerates triage and resolution compared to plain text.