/verify
Turn a code change into a prioritized browser-QA plan with Canary, then optionally record the flows.
> /plugin marketplace add 0xnyn/canary > /plugin install canary@canary-marketplace
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/verify
Context preview
What this command does when you run it.
Turn a code change into a prioritized browser-QA plan with Canary, then optionally record the flows.
Command definition
verify.mddescription: Turn a code change into a prioritized browser-QA plan with Canary, then optionally record the flows. argument-hint: "[ref range | description — blank = working-tree diff]"
Delegate to the `verify-agent` subagent. Scope: **$ARGUMENTS**.
If `$ARGUMENTS` is blank, verify the working-tree diff (`git diff` + `git diff --staged`). If it names a ref or range (e.g. `main...HEAD`, a branch, a PR), diff that. If it's a prose description of a change, reason from that. Ask it to read the diff, infer the affected user-facing workflows, and present a **prioritized QA plan** (P0/P1/P2 flows with the checks that must hold, phases as a guide). Then ask which flows to record — for approved ones, record a Canary session (`/canary:session` mechanics) and report each `report.html` with a one-line pass/fail. Offer `/canary:review` to open it. Already know the flow? Use `/canary:session`. Just a quick one-off with no plan? Use `/canary:run`.
QA harness built for Claude Code | E2E testing with screen recordings, console logs, network HARs, and Playwright traces
Repo: 0xnyn/canary
Other commands on canary.
- /review
Open the Canary session viewer and triage a recorded session.
Open command - /run
Automate a one-off browser task with Canary — navigate, click, scrape, screenshot — and return the result.
Open command - /session
Record a verifiable QA session (trace, video, HAR, console) and render a report.
Open command