Menu
Use when user asks to improve test coverage, find untested code paths, identify risky files without tests, or add missing test cases.
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 | test-coverage |
| description | Use when user asks to improve test coverage, find untested code paths, identify risky files without tests, or add missing test cases. |
Use this skill to systematically increase coverage while preserving behavior.
Measure current coverage: Collect total and per-file data.
Rank gaps: Prioritize low-coverage files with high risk or high churn.
Add focused tests: Cover error paths, boundary checks, and branch conditions.
Validate stability: Run fast suite first, then full suite if needed.
Summarize progress: Report before/after per file and residual gaps.
baselinenew_testscoverage_deltaremaining_gaps