PR

Write what a reviewer needs and the diff cannot show, check it mechanically, and open the PR only after the user confirms the exact text. Never merge, approve, or edit the branch's code.

Ground

1. Fix the base ref (for example origin/main) and read the whole git diff <base>...HEAD. If gh pr view <branch> --json state shows OPEN, read Update first.
2. Find the authority: the linked issue (gh issue view <n>) or a sealed .first-four-hours/blueprints/*/blueprint.md. Link or quote its intent, decisions, and acceptance criteria; never re-author them as a second source of truth. With neither, say so and take intent from the user.
3. From a clean worktree at the commit you will push, run each verification you will claim through record, one arg per argv element:

python <skill-root>/scripts/cli.py --repo-root <repo> --input runs=<runs.jsonl> \
  --input arg=<argv0> --input arg=<argv1> --format json record

Its result gives the real exit_code and the command string to cite.

Draft