audit-browser-tests

Audit browser test suites for stale tests, missing coverage, and flaky patterns.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/pnewsam/skills --skill audit-browser-tests-pnewsam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit-browser-tests
Source: https://github.com/pnewsam/skills/tree/main/archive/audit-browser-tests
Command: npx skills add https://github.com/pnewsam/skills --skill audit-browser-tests-pnewsam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Browser test suites drift out of sync with the application over time, leaving stale selectors, missing critical flow coverage, and flaky assertions that erode trust in end-to-end testing. This Skill audits an existing Playwright or Cypress suite against the current app and records findings in the standard epic planning flow. ## Core Features & Use Cases - Suite Cataloging: Detects the test framework, enumerates spec files, and records covered flows, selectors, routes, fixtures, and skipped tests. - Gap and Flake Detection: Identifies stale selectors, missing critical flows, hardcoded waits, weak assertions, and duplicate coverage. - Epic-Integrated Reporting: Writes an audit report to docs/epics and updates the browser-test coverage epic's Flow Inventory and child feature candidates. - Use Case: After a major UI refactor, run the audit to find which e2e tests no longer match current routes and which new user flows lack any browser coverage, then get a prioritized list of child features to plan. ## Quick Start Audit the browser tests in this repository and write the findings into the browser-test epic under docs/epics.

Frequently Asked Questions about audit-browser-tests

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

FAQPage Schema
How do I audit an existing browser test suite for missing coverage?▼

Run the audit to catalog every spec file, map covered flows and routes, then compare them against the current application. The result is an audit report in docs/epics listing missing critical flows, stale tests, and recommended child features.

Does this work with Playwright and Cypress test suites?▼

Yes, the audit detects the framework by checking for playwright.config or cypress.config files and package.json, then finds spec files under tests/, e2e/, or cypress/ directories. It records framework-specific selectors, fixtures, and skip patterns.

How to find flaky patterns in e2e tests?▼

The audit flags hardcoded waits, timing-sensitive assertions, and weak assertions during the comparison step. Each flaky finding is recorded with severity, evidence, and a recommended child feature for repair.

Will the audit modify my test files or source code?▼

No, the audit is read-only with respect to source and test files. It only writes the audit report under docs/epics and conservatively updates the browser-test epic's Flow Inventory and child feature candidates.

What happens if no browser-test epic exists yet?▼

The audit writes a provisional report such as docs/epics/browser-test-coverage-audit.md and recommends creating an epic using the plan-browser-tests structure. It does not create trackers outside the epic and feature planning flow.