ui-qa-pass
Runs a branch's app locally and drives a headless browser through the screens the change touches, choosing the states, themes, widths and roles by what the change could break. Takes a screenshot of each, fixes bugs and obvious polish as it goes with before and after shots, and writes a report that leads with the decisions the user needs to make. Use when the user says "QA this", "do a QA pass", "click through every changed screen", "screenshot every state", "test it in a browser and make a report", or before asking for review of a change people can see (app screens, marketing or docs pages, emails). Not for writing or fixing the automated browser test suite.
- Version
- 1.0.0
Pinned to revision 2d40eafe834d, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/ui-qa-pass/SKILL.md
- skills/ui-qa-pass/references/report-format.md
- skills/ui-qa-pass/references/screenshot-pitfalls.md
- skills/ui-qa-pass/references/state-matrix.md
- skills/ui-qa-pass/scripts/example_step.mjs
- skills/ui-qa-pass/scripts/run_step.mjs
Every link opens the file at its source, pinned to the revision this page describes.