Menu
Merge, push, sync after remote PR merge, or close out flow work with STATE and worktree cleanup. Invoke with /flow-finish.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | flow-finish |
| description | Merge, push, sync after remote PR merge, or close out flow work with STATE and worktree cleanup. Invoke with /flow-finish. |
| disable-model-invocation | true |
| metadata | {"flow":{"command":"/flow-finish"}} |
Triggered by: /flow-finish — also when the user requests merge/push/done outside the verify menu, or when /flow-verify menu options 1, 3, or 4 are chosen.
Integrate completed work and run Flow cleanup. Read and follow flow-shared/references/finish-gate.md (resolve via path resolver in flow/SKILL.md).
This skill is intentionally thin — finish-gate.md holds the checklists; this file routes intent and blocks raw git without cleanup.
| User intent | Action |
|---|---|
| "Merge back into main" / "merge locally" | Merge locally section in finish-gate |
| "Push the branch" | Push branch section |
| "Done for now" / pause without git | Done for now section |
| "PR merged on GitHub" / "sync local" / "clean up after PR" | Sync after remote merge section in finish-gate |
| Chose verify menu option 1 (push), 3 (merge), or 4 (done) | Same sections — verify already passed |
Do not use for: running tests or requirements checklist (that's /flow-verify), or branch review (verify option 2 / clean-code-reviewer).
/flow-verify, or user explicitly confirmsdocs/flow/STATE.md — confirm branch/topic matches current workBefore updating STATE: read flow-shared/references/session-gate.md (resolve via path resolver in flow/SKILL.md). Unrelated active STATE → session gate first.
finish-gate.md — prerequisites and STATE fields/flow-finish (no merge/push/sync/done phrase) → send the numbered finish menu from finish-gate Ambiguous /flow-finish; stop until user picks 1–4git fetch + git merge-base --is-ancestor — git only; forbidden: gh, polling, sync when check fails (see finish-gate Integration status — git only)STATE.mdchore/remove-flow-artifacts-<topic>, you commit and push for a PR into base (not a commit on base)gh or GitHub CLI/API for finish — integration status is git fetch + git merge-base --is-ancestor only; user rules preferring gh do not override/flow-finish without menu — do not guess sync or run gh when intent is uncleargit merge alone is not sufficient for active flow workphase: done after successful merge or pushgit branch -d instead) — remote sync may delete when user asked to clean upgit rm + git commit + git push on chore/remove-flow-artifacts-<topic>main/base — option 2 uses a chore branch only/flow-verify — options 1, 3, 4 read this skill or finish-gate.md for actionsworktree-setup.md — worktree removal rules defer to finish-gate merge pathShared prompts and references for flow-* skills. Not invoked directly.
Execute an approved plan with subagents, TDD, and two-stage review. Invoke with /flow-execute to resume or when plan exists without an active spec session.
Router for the flow development workflow. Invoke with /flow to triage and suggest the right /flow-* command.
Create an approved spec and self-reviewed implementation plan. Invoke with /flow-spec before multi-step work.
Small bounded changes with micro-spec, inline TDD, and per-task review. Invoke with /flow-patch.
Explore ideas and design before committing to a spec. Invoke with /flow-brainstorm when requirements are still fuzzy.