Repository Delivery

Overview

Deliver reviewed repository changes from a local worktree to the requested Git state. This is the sole owner of staging, commits, pushes, and other Git mutations after review acceptance. Verify branch policy, divergence, permissions, and staged content before mutation; never open a pull request.

Workflow

1. Read effective repository guidance first, including AGENTS.md, CLAUDE.md, and host-provided instructions when present.
2. Run git status --short --branch and identify branch, upstream, staged files, dirty files, and unrelated local work.
3. Fetch or inspect the relevant remote refs when network access is available; determine ahead/behind/diverged state before choosing push, rebase, merge, or squash behavior.
4. Confirm the requested delivery target: local commit only, push current branch, sync current branch, squash to main, delete temporary branch, or a narrower path scope.
5. Confirm branch policy and permissions: protected/default branch, force-push restrictions, required checks, branch naming, and whether direct updates are allowed or Not verified.
6. Ensure review is complete. Use repo-review first when ownership, mixed hunks, contract chains, or commit grouping are not already clear.
7. Run or reuse task-appropriate validation before staging unless the user explicitly requests delivery without further checks.
8. Stage only approved files or hunks, then inspect git diff --cached --stat, git diff --cached --name-status, and the staged diff.
9. Commit only the approved staged scope with the user's exact commit text when supplied; otherwise use the repository convention or a concise Conventional Commit.
10. Push, rebase, merge, squash, delete branches, or refresh from remote only when that action is the requested delivery target and the current divergence state supports the chosen operation.
11. Verify final local and remote state with branch, status, log, and remote ref evidence.