Command
/shipmates-qa
context → checklist → one step per turn → summary
Interactive local QA — one check per turn on a PR, issue branch, or named branch.
See it run
/shipmates-qa walk: the agent asks one check at a time; the captain types pass or a bug note.How to run it
Run it in your harness
/shipmates-qa <pr-number|issue-number|branch> [mode: risk|smoke] [platform hint]<angle brackets> = required · [square brackets] = optional
How it works
You drive the checklist; the captain operates the simulator, emulator, or device. No specialist board — this is human verification of a running build, not a diff review.
Intake
Parse PR, issue, or branch plus risk vs smoke and an optional platform hint. Announce the one-step-per-turn contract.
No spawn — parse and confirm the target.
Context
Boot from the diff, acceptance criteria, and the repo's run docs. Confirm how the captain will run the build.
Still the run — read the change, do not rewrite it.
Checklist
Build an ordered risk or smoke checklist privately. Gate out checks the named platform cannot run; prefer in-app toggles over OS network hacks.
The checklist stays in working memory — never dump it once one-at-a-time is in force.
Walk
Announce step N of M only. Wait for pass, fail notes, screenshot, or logs before advancing.
Captain operates the device; you log findings and do not repair.
Summarize
Per-step PASS/FAIL/DEFERRED plus product-impact-ready findings. Optional handoff and re-QA reuse the same checklist.
Report only unless the captain asks to file or re-QA.
Shared machinery — how commands work: worktrees, the CI gate, the review board, and merge modes.
When to use
- A change needs human eyes on a running build (offline states, chrome collisions, cold-start races).
- Diff / board review? /shipmates-pr-review. Automated gates? CI. Known defect repair? /shipmates-fix-bug.
The skill
The installer ships the full skill — stages, gates, config — from commands/shipmates-qa.md.