wsbaser:generate-bug-report

Generate HTML bug reports with verdicts, call chains, and code snippets.

1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/wsbaser/claude-plugins --skill wsbaser-generate-bug-report
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wsbaser:generate-bug-report
Source: https://github.com/wsbaser/claude-plugins/tree/main/plugins/wsbaser/skills/generate-bug-report
Command: npx skills add https://github.com/wsbaser/claude-plugins --skill wsbaser-generate-bug-report

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Automates turning bug verification data from conversations into a polished HTML report, ensuring consistent, shareable documentation for each bug.

Core Features & Use Cases

  • Generates a verdict HTML with MITIGATED/CONFIRMED/INCONCLUSIVE, a call chain, a network summary, and a code snippet.
  • Writes to .reports/{slug}.html for easy archival and review.
  • Suitable for single-bug verification workflows; pair with generate-test-report for multi-scenario suites.

Quick Start

Provide the bug verification details and run the generator to create .reports/{slug}.html.

Frequently Asked Questions about wsbaser:generate-bug-report

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

FAQPage Schema
How do I automatically generate an HTML bug report from verification data?▼

You can generate an HTML bug report by providing bug verification details from your conversation. The skill extracts verdicts, call chains, network summaries, and code snippets to output a polished .reports/{slug}.html file.

What is the best way to document a single-bug verification workflow in HTML?▼

Single-bug verification workflows are documented by extracting MITIGATED, CONFIRMED, or INCONCLUSIVE verdicts alongside call chains and network summaries. The process outputs a standardized HTML file for consistent archival and review.

How does automated bug report generation handle code snippets and network summaries?▼

Automated bug report generation parses conversation context to extract relevant code snippets and network summaries. These elements are injected into a standard report template to produce a structured HTML document.

Can I use this HTML report generator for multi-scenario test suites?▼

This HTML report generator is designed for single-bug verification workflows. For multi-scenario test suites, you should pair it with a separate test report generation tool to handle broader testing documentation.

Does the generated HTML bug report include a definitive verification verdict?▼

Yes, the generated HTML bug report includes a definitive verification verdict. It explicitly categorizes the bug status as MITIGATED, CONFIRMED, or INCONCLUSIVE within the standard report template output.

Where does the automated HTML bug report output get saved?▼

The automated HTML bug report gets saved directly to the .reports/{slug}.html path. This ensures easy archival and review by maintaining a consistent file structure for every generated bug report.