Menu
Use when user has fixed a bug and needs a test that proves it stays fixed, or when a failure needs to be captured as a reproducible test case.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when user asks to check browser state, debug page errors, inspect network traffic, take screenshots, automate clicks or form fills, run accessibility or security audits, measure performance, generate tests, or record browser sessions. Trigger phrases: "check my browser", "debug this page", "take a screenshot", "browser errors", "network requests", "automate the browser", "record a test", "accessibility audit", "performance check", "what's on the page".
Use when the user wants a full Kaboom quality audit of a web app or tracked site, with one polished report covering Functionality, UX Polish, Accessibility, Performance, Release Risk, and SEO.
Use when user says "QA my app", "find all bugs", "check my app for problems", "debug my whole app", "what's broken", or wants a comprehensive quality review of their web application.
Use when user asks to check API responses, validate request/response contracts, compare API behavior against a spec, or detect schema drift.
Use when user asks to automate browser actions, click buttons, fill forms, navigate pages, run a sequence of browser steps, or build a repeatable workflow.
Use when MCP tools fail to connect, user reports "extension not connected", tool calls return errors, or user asks to check their Kaboom setup.
| name | regression-test |
| description | Use when user has fixed a bug and needs a test that proves it stays fixed, or when a failure needs to be captured as a reproducible test case. |
Use this skill after a bug is confirmed and should never reappear.
Reproduce failure deterministically: Capture exact trigger and expected assertion.
Pick narrowest test layer: Prefer unit/integration before full e2e unless browser behavior is required.
Build stable fixtures: Use fixed inputs, bounded timing, and mocked unstable dependencies.
Write fail-first assertion: Ensure test fails on pre-fix behavior and targets the real defect.
Add guard assertion: Assert adjacent behavior to prevent overfitting.
Verify repeatedly: Run targeted tests multiple times to catch flakiness.
test_locationfailure_assertionregression_guardstability_controlsverification_results