What /source-control:pull-request full adds over running prep, create, ready, monitor, and merge
by hand: the phase-to-phase handoff state and the abort points. Read it only when the invocation
carried full; every other action routes through the phase table in ../SKILL.md.
Run Phase 1 → Phase 2 → Phase 2.5 → Phase 3 → Phase 4 as one continuous flow, pausing only at decision gates where the outcome could vary and at one interactive-only checkpoint at the create boundary.
Phase 2.5 sits between create and monitor. Inside full, Phase 2 opens a draft and leaves the flip to this step; when the invocation asked for a draft, full ends after create instead. Phase 2.5 reviews and verifies the updated head and flips it out of draft (ready-for-review.md); Phase 3 monitors the CI and review activity the flip starts. Without the flip, monitor watches a draft no reviewer has been asked to read.
Create→ready checkpoint (full only):
After Phase 2 reports the PR URL, detect session mode:
- Interactive (no autonomous-session marker like
CLAUDE_CODE_REMOTE=true): ask whether to proceed to Phase 2.5 (ready) and Phase 3 (monitor) in this session. Responses: proceed (continue to Phase 2.5) / stop (end after create, leaving the draft) / handoff (end; another session/routine picks up the flip and monitoring). No response means stop. - Autonomous (
CLAUDE_CODE_REMOTE=trueor equivalent): continue to Phase 2.5 without a prompt; there is no user to ask.
Standalone create (not invoked inside full) ends after Phase 2, and after Phase 2.5 when its open state is ready; when its session keeps acting on the PR, it arms event delivery first. See reference/create.md §2.6.
Decision gates (pause for user):
| Gate | Why it needs input |
|---|---|
| Prep findings have VALID fixes | User decides which to fix vs defer |
| Commit message content | User may want different wording |
Create→ready (interactive only, full mode) |
User may want to hand off the flip and monitoring to another session/routine |
| CI failure fix proposal | Fix approach has multiple options |
| Merge confirmation | Irreversible action |
Not gates (proceed automatically):
| Transition | Just do it |
|---|---|
| Prep complete → create | Obvious next step |
| Ready flip verified → monitor | The flip is what starts the review round |
| All readiness gates pass → suggest merge | Report with full readiness verdict |
| Comment classified INCORRECT → react + reply | Evidence already gathered |
| Fix pushed → re-monitor | New push = new cycle |
Never auto-proceed on these (even in full mode):
| Condition | Why it's not a gate pass |
|---|---|
| CI green + no comments yet | Reviewers may not have posted. Cooldown required |
| CI green + failing security scan | Security findings must be evaluated before merge |
| CI green + unclassified failures | Every FAILURE needs explicit classification |
In a non-interactive context (cloud session, CI action), minimize gates to merge-only.