Guides

The agent walks the acceptance plan on local or review, QAwalk captures every screen and e-mail, checks the criteria and puts one canvas link into the PR. The reviewer accepts or returns it there.

Run the flows against staging, compare with the baseline run the team accepted, and see what moved: step statuses, criteria, evidence, pixels.

A read-only run of your public pages as a visitor: headings, metadata, hreflang, Open Graph, structured data, overflow, console. Shared, compared with yesterday, fixed before anyone else notices.

Sign-up confirmation, order receipt, password reset. QAwalk captures the e-mail from Mailpit or letter_opener as a step of the flow, checks its subject and links, and shows it on the canvas next to the form.

How Claude Code runs QAwalk: the skill it installs, what it may do without asking, what it asks first, the prompts that work, and how it reads reviewer feedback and the inbox.

How Codex runs QAwalk: where the skill lives, how AGENTS.md points to it, the prompts that work, and how Codex reads reviewer feedback before it continues.

Run the same walkthrough from GitHub Actions or any CI: bundled Chromium, a tester token to share, a read-only token to read, results in the PR and on the canvas.

What the qawalk skill makes an agent do, what each reference covers, and which third-party skills and tools fit alongside, each with its implications: what runs where, which data leaves the machine, when not to use it.