skills.rest
patrob
patrobCOMMUNITY
Explore all skills by this author →
𝕏@patrobdevGitHub

pw-bug-hunt

Run parallel hypotheses to isolate root causes and require failing tests before patching.

Updated Apr 14, 2026
Search Tags:#code-review#workflow-orchestration#root-cause-analysis#test-driven-development#bug-fix#parallel-investigation
One-click install
npx skills add https://github.com/patrob/skills --skill pw-bug-hunt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pw-bug-hunt
Source: https://github.com/patrob/skills/tree/main/plugins/claude-skills/skills/pw-bug-hunt
Command: npx skills add https://github.com/patrob/skills --skill pw-bug-hunt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bug-prone software often suffers from slow triage and fragmented fixes. This Skill orchestrates a structured, parallel hypothesis workflow to quickly identify root causes, generate failing tests, and drive minimal, verifiable patches.

Core Features & Use Cases

  • Parallel hypothesis exploration with multiple, independent investigations to surface root causes.
  • Failing test generation and documentation to reproduce and validate fixes.
  • End-to-end verification workflow including test execution and quality checks before deliverables.
  • Use Case: When a bug is reported or a test fails, trigger 2-3 parallel investigations, collect evidence, determine the root cause, write a failing test, implement a minimal fix, and verify the outcome.

Quick Start

Provide a bug description, an error message, or a failing test name to start the bug-fix workflow.

Frequently Asked Questions about pw-bug-hunt

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

FAQPage Schema
How do I automate bug triage and find a root cause faster?▼

Automating bug triage involves running parallel hypothesis investigations to quickly isolate the root cause. This process coordinates independent investigations, collects evidence, and identifies the underlying issue before any code changes are attempted.

What's the best way to fix a bug using test-driven development?▼

The best way to fix a bug using test-driven development is to require a failing test before applying a patch. This workflow ensures you generate a failing test to reproduce the issue, implement minimal code changes, and execute end-to-end verification.

Can I use parallel investigation for resolving failing tests across projects?▼

Yes, parallel investigation is applicable to failing tests across projects. It triggers 2-3 independent investigations simultaneously to surface root causes, enabling rapid root-cause isolation and validation regardless of the specific project.

How do I start a bug-fix workflow from an error message?▼

To start a bug-fix workflow from an error message, simply provide the error message, a bug description, or a failing test name. The workflow then initiates structured hypothesis-driven exploration to document the root cause and validate the fix.

Why does parallel hypothesis exploration help with bug fixes?▼

Parallel hypothesis exploration helps with bug fixes by running multiple independent investigations to surface root causes rapidly. This structured approach overcomes slow triage and fragmented fixes by isolating the actual issue before generating a failing test.

Related Skills

Explore More Software Engineering Skills→
Design-System-ETDesign-System-ET

debugging-wizard

Parse error messages and stack traces to isolate root causes.

Official
Advanced
paulbrittainpaulbrittain

run-smoke-tests

Run Playwright smoke tests and rerun until stable with traces and logs.

Community
Intermediate
nguyenthienthanhnguyenthienthanh
24

bugfix-quick

Fix software bugs via a four-step TDD workflow with test verification.

Community
Basic
dimsourdimsour
2

investigate

Spawn parallel subagents to analyze reproduction, root cause, impact, and fix strategy.

Community
Advanced