Done

Take the current task to an observable merged state. Manual invocation is explicit authorization to commit, push, create or edit a PR/MR, merge it, and mutate directly related issues. It does not authorize force-pushes, protection bypasses, unrelated edits, or other external writes.

Treat user arguments as optional scope, issue context, or merge-method preferences. Otherwise infer scope from the current conversation and repository evidence.

Process

1. Establish the closure contract. Resolve the git root, forge from the remote URL, authenticated user, default branch, current branch and upstream, worktree layout, dirty state, and any open PR/MR for the branch. Store the resolved forge default branch as DEFAULT_BRANCH and use that value consistently below; never assume a fixed branch name. Define the intended change set from the current task; preserve unrelated work unstaged. If intended and unrelated edits cannot be separated safely, ask one precise question before any external write.

   Completion criterion: the forge, resolved DEFAULT_BRANCH, intended paths, unrelated paths, existing review state, and local default-branch worktree are accounted for.

2. Validate the intended change. Read the full diff and repository instructions. Run the smallest relevant checks after the final edit, including tests, lint, build, or generated-file checks required by the changed surface. Fix failures caused by the intended change; stop with the exact blocker when a green result requires broader scope or unavailable infrastructure.

   Completion criterion: every intended change is represented in the diff, required artifacts are present, and no relevant check is red.

3. Commit and push. When on DEFAULT_BRANCH or detached HEAD, create a codex/<short-slug> branch without disturbing the working tree. Follow recent commit-message style and split independent concerns into atomic commits. Stage only the intended paths, inspect the staged diff, commit, and push with upstream tracking. Resolve ordinary remote divergence without rewriting published history.

   Completion criterion: every intended change is in a remote-reachable commit and unrelated local changes remain untouched.