skills.rest
jerelvelarde
jerelvelardeCOMMUNITY
Explore all skills by this author →
GitHub

create-bug-report

Generate structured markdown bug reports with reproduction steps and environment details.

6|Updated Feb 19, 2026
Search Tags:#documentation#triage#issue-tracking#reproduction-steps#bug-report#environment-details
One-click install
npx skills add https://github.com/jerelvelarde/chalk-skills --skill create-bug-report-jerelvelarde
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-bug-report
Source: https://github.com/jerelvelarde/chalk-skills/tree/main/skills/create-bug-report
Command: npx skills add https://github.com/jerelvelarde/chalk-skills --skill create-bug-report-jerelvelarde

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a structured bug report from user-reported issues, ensuring reproducible steps, environment details, and a clear distinction between expected and actual behavior.

Core Features & Use Cases

  • Generate a complete bug report including reproduction steps, environment details, observed vs expected behavior, severity, and triage notes.
  • Support workflows for filing issues, documenting defects, or handing off to engineering and QA with a consistent Markdown artifact.
  • Enforce a standardized structure that improves triage speed and reduces back-and-forth during bug fixing.

Quick Start

Provide a detailed bug description: what happened, what you expected, steps to reproduce, and environment details.

Frequently Asked Questions about create-bug-report

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

FAQPage Schema
How do I create a structured bug report with reproduction steps and environment details?▼

To create a structured bug report, provide a detailed description of the issue, including reproduction steps, environment details, and expected versus actual behavior. This generates a standardized Markdown artifact with all required triage fields for engineering workflows.

What fields should be included in a bug report for engineering and QA handoff?▼

A bug report for engineering handoff should include a descriptive title, environment details, steps to reproduce, expected and actual behavior, error output, bisect hints, impact assessment, and related issues. This structure reduces back-and-forth during bug fixing.

How does standardizing issue tracking format improve triage speed?▼

Standardizing issue tracking format improves triage speed by enforcing a consistent Markdown structure with reproducible steps and risk assessment. This ensures development and QA teams receive actionable tasks with all necessary environment and behavior details.

Can I generate a bug report file directly for issue tracking documentation?▼

Yes, you can generate a bug report file directly for issue tracking documentation. The output is formatted as a Markdown file named with a numeric prefix and saved in the docs engineering directory for immediate workflow integration.

What is the best way to document expected vs actual behavior in a defect report?▼

The best way to document expected versus actual behavior in a defect report is to provide a clear distinction between the two within a structured format. Including specific error output and bisect hints further clarifies the defect for engineering triage.

Related Skills

Explore More Software Engineering Skills→
Andreicr1Andreicr1

report-bug-ce

Collect bug details and create a GitHub issue for the compound-engineering plugin.

Community
Advanced
jerelvelardejerelvelarde
6

triage-bugs

Analyze bug reports to determine severity, priority, and component ownership.

Community
Advanced
xotongxotong

ce-report-bug

Automate structured bug reporting for the ce plugin via GitHub issues.

Community
Advanced
w95w95
145

escalation

Structure support escalation briefs with context, reproduction steps, and business impact.

Community
Intermediate