commit-push-pr

See REFERENCE.md for gates, commits, labels, body, evidence.

Only explicit merge requests use the merge contract, not this PR flow.

Preflight

1. Inspect git status -sb, git diff HEAD, branch, recent log, and branch PR.
2. Resolve endpoint: commit only, push (--no-pr), or PR. Commit-only skips remote and gh preflight.
3. Push/PR needs a remote; PR also needs authenticated gh and the default branch.
4. For PR, run gh stack view --json; inspect base/stack. A normal PR owns one layer, never gh stack submit.
5. Run applicable review axes inline; do not block merely over named skill invocation.
6. Runnable PR work requires current /dogfood PASS; BLOCKED needs user waiver.
7. Stage requested paths by purpose; ask if ownership is unclear.

Commit