bug-detail

Automates bug reproduction with Playwright and generates a detailed report file.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Mar5929/.claude --skill bug-detail
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-detail
Source: https://github.com/Mar5929/.claude/tree/main/skills/bug-detail
Command: npx skills add https://github.com/Mar5929/.claude --skill bug-detail

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In QA workflows, vague bug reports are transformed into concrete investigation tasks by automatically opening the app with Playwright, reproducing issues, collecting evidence, and generating a detailed bug report.

Core Features & Use Cases

  • Reproduce bugs across environments using automated browser sessions
  • Gather console logs, network traces, DOM state, and screenshots to support findings
  • Produce comprehensive bug reports and optionally create GitHub issues for traceability

Quick Start

Launch a new investigation by starting the app in a test environment and providing the bug description.

Frequently Asked Questions about bug-detail

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

FAQPage Schema
How do I automate bug investigation and collect evidence with Playwright?

Automate bug investigation by using Playwright to open the app, reproduce issues, and gather console logs, network traces, DOM state, and screenshots to produce a thorough bug report.

What is the best way to generate detailed bug reports from vague user descriptions?

Transform vague bug reports into concrete investigation tasks by automatically reproducing the issues in a test environment and collecting comprehensive evidence for a detailed report.

How do I create GitHub issues automatically from bug investigation results?

After collecting evidence during the bug investigation, the workflow generates a shareable bug report file and can optionally create a GitHub issue for traceability.

Can I reproduce bugs and collect network traces for standalone and BEF-enabled projects?

Yes, you can reproduce bugs across environments using automated browser sessions, gathering network traces and DOM state for both standalone and BEF-enabled projects.

How does this bug investigation workflow handle sensitive data and credentials?

The bug investigation workflow ensures safe data handling by avoiding credential leakage and using environment references for configuration.

What evidence do I need to collect to reproduce a bug in a test environment?

To reproduce a bug, collect console logs, network traces, DOM state, and screenshots by starting the app in a test environment and providing the bug description.