---
requires: code on branch
produces: PR ready, assigned to its reviewer to merge
---
Submit the current branch for review and manual merge. Rebase, clear scratch, create/update the PR, mark it ready, and assign it — then stop. The reviewer clicks merge.
Use `pr-submit` (not `pr-land`) whenever the user will merge the work.
`pr-land` is for headless/auto runs where loopflow merges hands-off;
`pr-submit` leaves the one required merge click to the user. (GitHub blocks
approving your own PR, so the gate is the merge click, not a review approval —
the button unlocks once checks pass.)
Tracked Tasks use the same command. Delivery state records the user-owned
exact-head merge request, but `pr-submit` does not install, advance, or inspect
the Task's Flow position.
## Orientation
Before starting, orient yourself in this branch:
- Read `scratch/` — design docs and notes for the current work live here
(`scratch/<branch>.md` is this PR's design; `scratch/questions.md` holds open
questions and assumptions).
- Read wave/PM context only when the seed names the exact wave, task, project,
or a concrete coordination question; never infer it or repair access as a
prerequisite.
- Read the repo's agent doc (`CLAUDE.md` / `AGENTS.md`) for conventions.
Write design artifacts, notes, and open questions under `scratch/`. Don't
re-derive what these already record.
## API
`lf pr submit` handles the entire mechanical workflow: staging uncommitted changes, rebasing, creating or updating the PR, marking it ready, and assigning it to the user who will merge. It does **not** arm auto-merge.
```
lf pr submit [--create-pr] [-m "commit message"] [--title "..."] [--body "..."]
```
Inside a managed Task worktree, `-c` completes the Task after the manual merge
and `--next <slug>` rotates its serial PR chain after merge.
**Do not run git commit, git push, gh pr create, or gh pr ready directly.** `lf pr submit` does all of this. Running those commands manually skips the assignment and leaves the PR in an inconsistent state.
## Workflow
### 1. Understand the branch
```bash
git log origin/main..HEAD --oneline
git diff origin/main...HEAD --stat
```
Check `scratch/` for context. If `scratch/<branch>-review.md` exists (from gate), use it to understand the change and inform the PR body.
Stage and include all changes — committed and uncommitted — in the PR. If the working tree is dirty, compose a commit message for the uncommitted changes (pass it as `-m` in step 3). Never ask which files to include; everything on the branch ships together.
### 2. Prepare PR copy
If `scratch/pr-title.txt`, `scratch/pr-body.md`, and `scratch/.pr-copy-ref` exist (from `lf gate`), `lf pr submit` reuses them automatically.
If those files are missing or stale, write title/body manually and pass `--title` + `--body`.
Keep the title and opening summary focused on the benefit of this PR's actual
change. Preserve command spelling and proper names; use an area prefix only
when it helps recognition. Follow with minimal **What changes**, then **Why it
matters** only if needed, and material limits. Keep automated test and lint results
in **Checks** or CI. Put **Try it** last when useful: a user action and its visible
result, never tests, test commands, or test results. Distinguish suggested steps
from observed behavior and label simulations. Small changes may need only a summary
and walkthrough. Reconcile changed scope instead of appending history. Loopflow adds
Task identity and merge consequences; do not repeat or invent them.
### 3. Submit
```bash
lf pr submit --create-pr
```
If you wrote title/body manually, include them:
```bash
lf pr submit --create-pr --title "<title>" --body "<body>"
```
Include `-m "<message>"` if the working tree was dirty in step 1.
If `lf pr submit` fails due to rebase conflicts, launch a sub-agent to run the
`rebase-conflicts` skill, then retry `lf pr submit`.
## Notes
- The PR is left ready and assigned — the assignee's merge click lands it. Don't enable auto-merge or merge on their behalf.
- If the PR already has a good title and body, run `lf pr submit` without `--title`/`--body` to keep existing content.
## Adaptation
If you discovered repo-specific submit conventions — assignee, branch
protection rules, CI wait behavior — encode them. Most belong in repo docs
where all skills benefit. Copy this skill to `.lf/skills/pr-submit.md` when the
repo needs submission to work differently.