bug-report

Name: bug-report
Availability: InStock
Author: clawpod-app

Generate structured bug reports with reproduction steps and severity assessments.

46|11|Updated Mar 29, 2026

Search Tags:#qa #severity #issue-tracking #reproduction-steps #bug-report #defect-management #environment-details

Ready to run

npx skills add https://github.com/clawpod-app/awesome-openclaw-agent-packs --skill bug-report-clawpod-app

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bug-report
Source: https://github.com/clawpod-app/awesome-openclaw-agent-packs/tree/main/packs/qa/skills/bug-report
Command: npx skills add https://github.com/clawpod-app/awesome-openclaw-agent-packs --skill bug-report-clawpod-app

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The bug-report skill helps teams transform vague user feedback into precise, reproducible defect reports with prioritized severity, saving time in triage and reproduction.

Core Features & Use Cases

Structured Bug Report: captures Title, Severity, Component, Environment, Description, Steps to Reproduce, Expected vs Actual behavior, and Evidence.
Reproducible Workflows: guides testers to produce deterministic steps and gather logs/screenshots.
Use Case: when a user reports "it's broken," generate a formal report suitable for issue trackers and developer queues.

Quick Start

Describe the bug scenario in plain language and generate a complete report with steps to reproduce, environment, and evidence.

Frequently Asked Questions about bug-report

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

FAQPage Schema

How do I write a bug report with clear reproduction steps from vague user feedback?▼

To write a bug report with clear reproduction steps, describe the vague issue in plain language to generate a structured defect report capturing deterministic steps, environment details, and evidence for issue trackers.

What should be included in a structured bug report for issue tracking?▼

A structured bug report should include the Title, Severity, Component, Environment, Description, Steps to Reproduce, Expected versus Actual behavior, and Evidence to ensure the defect is actionable for developer queues.

How do I assess bug severity during issue triage?▼

Assess bug severity during issue triage by converting vague product feedback into a standardized report that evaluates impact and includes environment details alongside reproduction steps for accurate prioritization.

Can I generate defect management reports from plain language descriptions without technical logs?▼

Yes, you can generate defect management reports from plain language descriptions by transforming the text into a formal report with deterministic reproduction steps and evidence sections, even without initial technical logs.

What is the best way to format environment details for software defect reports?▼

The best way to format environment details for software defect reports is to capture them within a standardized template that pairs the environment context with reproduction steps and severity assessments for reproducible workflows.