push

effort: medium name: push description: | Commit and push changes to the remote ("commit and push", "push this", "ship it", "save and push", "push"). The agent inspects the diff and picks single-commit or atomic mode automatically: atomic when changes span unrelated units (mixed categories, multiple distinct areas), single commit for one focused change. Do NOT create a pull request. user-invocable: true allowed-tools: Bash(git diff:), Bash(git status:), Bash(git log:), Bash(git add:), Bash(git commit:), Bash(git push:), Bash(git branch:*)

Commit the current working tree's changes and push them to the remote.

Mode selection

Inspect status + diff and pick the mode yourself — do not ask the user:

Use atomic when the diff spans clearly distinct units: multiple unrelated files/areas, a mix of categories (feature + fix + docs + refactor), or > ~5 files that don't share a single theme.
Use single commit for one focused change: a single file, a single feature/fix/refactor, or trivial edits (typos, formatting, version bumps, lockfile-only).
When borderline, prefer single commit — atomic only when separation is genuinely useful.

State the chosen mode in one short line before staging (e.g., "Atomic — 3 commits: feature X, fix Y, docs Z") so the user can correct it.

Context

Current git status: !git status
Current git diff (staged and unstaged): !git diff HEAD 2>/dev/null || git diff --cached
Recent commits (for message style): !git log --oneline -10

Commit message convention

Match the repo's existing commit style exactly — study git log --oneline -10 from Context for prefix style (e.g., feat:, fix:, imperative verb), capitalization, punctuation, and tone. Do not invent your own convention.

Workflow — single commit (default)

Stage changes — review the diff for secrets, credentials, or junk files (.env, *.log, node_modules, etc.). If any are present, stage only the safe files with git add <paths>. Otherwise, git add -A is fine.
Commit — write a concise message that follows the repo's convention. Focus on what changed and why, not listing every file. Use a HEREDOC for the message to preserve formatting.
Push — run git push. If no upstream is set, use git push -u origin HEAD.

Workflow — atomic

Group all changes into logical units (feature/fix/refactor/docs/etc.).
For each unit:
- Stage only the relevant files (git add <paths>). Do NOT use git add -p — it requires interactive input.
- Sanity-check the staged diff (git diff --cached).
- Commit with a concise message strictly matching the repo's convention.
Repeat until all changes intended for this push are committed. If any files are intentionally left uncommitted, tell the user before pushing.
Push the current branch (git push). If no upstream is set, use git push -u origin HEAD.

Constraints

If there are no changes to commit, say so and stop.
Do NOT create a pull request.
Do NOT rebase, squash, or amend unless explicitly asked.
If git push is rejected (e.g., non-fast-forward), report the error and stop. Do NOT force-push.
In atomic mode, if changes cannot be cleanly separated, explain why and prefer fewer commits over tangled ones.