Submit

Take the branch from "I am happy with it" to a change request ready for a person to review and merge. The user's invocation authorizes the commit, the push, and opening or updating the change request; the merge stays with the reviewer, whatever merge actor or invocation approval workflow.md records. Load each dependency named below through the available skill invocation mechanism or its installed SKILL.md; when one is not installed, follow the fallback given with it and report the missing skill as a gap.

Once the change request is registered with the harness, tell a pause from a stop. Step 4's wait for the watcher is a pause: keep the registration, end the turn, and resume when the watcher wakes you. Every other stop ends the run, including the final report: stop watching the change request first so control returns to the user.

Read docs/agents/code-host.md for delivery operations, docs/agents/workflow.md for the delivery mode, base branch, review equivalent, and the transitions it assigns after the merge, and, when the work links tickets, docs/agents/issue-tracker.md for linking them. workflow.md is authoritative for the base branch; take it from code-host.md only when workflow.md does not record it. Reuse their unchanged contents from context. Without them, use the repository's contribution rules and the host CLI.

Choose the route before any remote or change-request operation. Use the hosted change-request route unless the repository explicitly configures local delivery, branch-only delivery, or another review equivalent; those use Review without a change request below instead of steps 3 through 5. A local destination makes the run local-only: use local refs and operations throughout, with no fetch, push, or code-host calls.

Resolve the delivery base before changing branches: the user's branch argument, then the configured base branch, then the default branch. Record the intended changes: the user's request plus any cleanup or review record, else the batch step 1 finds. Keep cleanup's review base and checked content so its batch can be told from inherited branch history; when committing leaves that content unchanged, reuse its check record.