write-bug-report

Generate structured bug reports from raw descriptions with mandatory sections.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/hpsgd/claude-marketplace --skill write-bug-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-bug-report
Source: https://github.com/hpsgd/claude-marketplace/tree/main/plugins/engineering/qa-engineer/skills/write-bug-report
Command: npx skills add https://github.com/hpsgd/claude-marketplace --skill write-bug-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write-bug-report provides a structured, repeatable framework to convert vague bug descriptions into actionable defect reports with explicit steps, evidence, and severity.

Core Features & Use Cases

  • Systematic evidence gathering and reproduction steps.
  • Root-cause analysis and actionable remediation guidance.
  • Applies to software development, QA triage, and incident response to standardize reporting.

Quick Start

Describe a concrete bug scenario and run the tool to generate a structured report.

Frequently Asked Questions about write-bug-report

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

FAQPage Schema
How do I write a structured bug report from a raw defect description?

To write a structured bug report, you convert raw descriptions into a standardized template that enforces mandatory sections for reproduction steps, environment, evidence, and severity. This ensures defect reports are actionable and deterministic.

What is the best way to document incident response and QA triage for software defects?

The best way to document incident response and QA triage is to use a repeatable framework that captures systematic evidence gathering, detailed reproduction commands, and severity classification to standardize defect reporting across teams.

Can I use a bug report template to enforce mandatory reproduction steps and environment details?

Yes, an effective bug report template enforces mandatory reproduction steps and environment details. It requires explicit evidence gathering and detailed reproduction commands to ensure deterministic reviews and actionable remediation.

How does root-cause analysis integrate with bug report generation?

Root-cause analysis integrates with bug report generation by linking systematic evidence gathering and reproduction steps to actionable remediation guidance. This helps developers trace defects directly from observed incidents to underlying causes.

What should be included in incident documentation for software development to ensure deterministic reviews?

Incident documentation should include explicit steps, environment details, evidence, and severity levels. Using a reproducible template with detailed reproduction commands ensures deterministic reviews during software development and QA triage.

Why do vague bug descriptions fail during QA triage and how can I fix them?

Vague bug descriptions fail during QA triage because they lack reproducible steps and evidence. You fix them by applying a structured template that mandates detailed reproduction commands, environment specifics, and severity classification.