burst-bug-hunter

Run persistent multi-step Playwright bursts against live apps.

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/migletto/slides --skill burst-bug-hunter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: burst-bug-hunter
Source: https://github.com/migletto/slides/tree/main/.claude/skills/burst-bug-hunter
Command: npx skills add https://github.com/migletto/slides --skill burst-bug-hunter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, and includes assets (resource) components.

What problem does it solve?

This Skill speeds up browser-based bug hunting by replacing slow, one-action-at-a-time agent loops with persistent, multi-step Playwright bursts that run unattended and return a single structured result.

Core Features & Use Cases

  • Warm browser sessions keep the app open once so repeated checks are faster and more consistent.
  • Burst-based execution lets you submit full scripts for complex exploratory or verification flows instead of predicting every click separately.
  • Reset and evidence capture support repeatable scenarios, screenshots, and immediate logging of findings during an active hunt.
  • Use case: Validate a suspected UI regression in a live web app, capture proof screenshots, and record the defect before the hunt window expires.

Quick Start

Upload the burst-bug-hunter skill, point it at your app and repo config, and ask the agent to run a defensive Playwright burst that verifies the target flow and records any findings.

Frequently Asked Questions about burst-bug-hunter

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

FAQPage Schema
How do I run multi-step Playwright bursts for exploratory browser testing?

Multi-step Playwright bursts run unattended against a live app by submitting full scripts to a persistent warm browser session, returning structured results and screenshot evidence instead of executing one action at a time.

What is a warm browser session for bug hunting?

A warm browser session keeps your application open persistently so repeated Playwright checks execute faster and more consistently during exploratory testing, eliminating the overhead of relaunching the browser for every action.

How do I capture screenshot evidence during automated regression testing?

Screenshot evidence is captured automatically during Playwright burst execution by logging findings and recording proof screenshots immediately when a UI regression or defect is discovered in the active hunt window.

Do I need a running server to use Playwright for time-boxed defect discovery?

Yes, time-boxed defect discovery requires a warm server, repo-provided app configuration, and reset support to ensure repeatable scenarios and accurate verification during persistent browser automation bursts.

Can I use burst execution instead of single-action agent loops for UI verification?

Yes, burst-based execution replaces slow single-action agent loops by allowing you to submit full multi-step Playwright scripts for complex exploratory or verification flows, returning a single structured result unattended.

What are the limitations of using persistent browser sessions for bug hunting?

Persistent browser sessions require applications to support reset functionality for repeatable scenarios, and the target application must be browser-drivable via Playwright automation to execute multi-step bursts and capture evidence.