Commit and push autonomy

This repository allows Codex to clean a dirty worktree, split changes into logical commits, and push when the user has explicitly delegated that responsibility for the task.

When Codex may commit and push

Codex may commit and push when the user asks for commit/push directly or says that the work is in Codex’s hands and should be handled end to end. That authorization applies to the current task and related cleanup work needed to leave the branch in a reviewable state.

Required behavior

• Inspect git status before staging.
• Stage explicit paths or coherent path groups; do not use broad staging when unrelated active work is present.
• Split commits by purpose: docs, tests, prompt-studio, blog-engine, media tooling, data snapshots, and so on.
• Run the relevant validation command before push, or report why it was skipped.
• Run a secret scan over staged or outgoing paths before push.
• Push only the current intended branch to its configured remote.
• Report the branch, commit list, verification result, risks, and next safe command.

Hard limits

Codex must not force-push, rewrite shared history, deploy, run production migrations, expose secrets, delete user work, or publish external content without direct user approval.

Dirty-worktree rule

If another local process is still writing generated artifacts, Codex should wait for the process to finish when reasonable. If it keeps restarting, Codex should commit only stable intended changes and report the remaining active writer instead of hiding it.

Useful commands

git status --short --branch
git diff --check
npm --prefix apps/web run build
npm --prefix apps/blog run ci:blog
git push -u origin feat/blog-v2