What problem does it solve? Automated tests and CI pipelines do not prove that a change actually works for users. This Skill closes that gap by creating a structured QA plan from tickets and diffs, executing the checks in a real environment, and reporting evidence-backed results. ## Core Features & Use Cases - Risk-Based QA Depth: Selects smoke, focused, or full coverage based on change risk, from docs-only edits to checkout and auth flows. - Diff-Driven Regression Checks: Automatically adds regression coverage for shared components, stores, GraphQL queries, feature flags, and files outside the ticket scope. - Evidence-Based Reporting: Executes checks against preview URLs or local environments and records concrete evidence such as URLs, viewports, console output, and network payloads. - Use Case: After finishing a Jira ticket that changes a pricing component, run this Skill to validate the acceptance criteria in the preview deployment, check one adjacent consumer of the shared component, and produce a pass/fail report with evidence before PR handoff. ## Quick Start Ask the agent to run manual QA on the current PR or ticket, providing the ticket link and preview URL so it can plan, execute, and report the checks.
