What problem does it solve? Code changes can silently break page rendering, console output, API responses, or component behavior, and manually clicking through every affected page after each change is slow and error-prone. This Skill automates regression verification in a real browser while enforcing strict safety rules around destructive or billable actions. ## Core Features & Use Cases - Scope-driven impact analysis: Derives affected pages from uncommitted changes, branch diffs, or custom targets by mapping changed files to router definitions and reverse-looking-up API consumers. - Real-browser verification: Uses chrome-devtools MCP to navigate pages, check console for errors and warnings, inspect snapshots and network requests, and exercise side-effect-free interactions. - Safety-gated operations: Honors per-environment forbidden_actions, treats undefined environments as read-only, and requires user approval before any create/update/delete, billing, or notification action. - Cross-environment triage: Reproduces discovered issues on an environment without the changes to determine whether they are change-caused, pre-existing, or environment-caused. - Use Case: After modifying a shared UI component and an API handler, run the Skill to identify all impacted pages, confirm console cleanliness and correct rendering on each, and receive a report table of check items × pages × results. ## Quick Start Ask the AI to run browser-test to verify in the browser that your current uncommitted changes cause no regressions on the affected pages.
