Commit and push the current branch

Ship the working tree on the branch that is checked out. This skill never creates or switches branches. Explicit invocation on a branch, including the default branch, authorizes the push to that branch. For a feature branch off the default, use commit-push-pr in its no-PR mode. When the invocation names the default branch as the target, run in commit-push-main mode: only the resolved default branch is pushed, the remote default branch is verified before any commit, and any other checked-out branch is refused.

Contract

Field	Bound contract
Trigger	A human explicitly invokes this skill to commit and push to the checked-out branch, or names the default branch as the push target (commit-push-main mode).
Authority	Human-only: explicit human invocation is the authorization. The skill previews the exact push target and the commit set before the push. The write set is local commits on the checked-out branch and one push to origin/<current-branch>; in commit-push-main mode that target is origin/<default> and any other branch is refused. Rollback is git reset --hard <prior-HEAD> for new commits and a revert commit for pushed work. No remote mutation beyond the previewed push.
Side effect	Local commits on the checked-out branch and one git push to origin/<current-branch>; in commit-push-main mode that target is the verified origin/<default> and the commit follows the remote preflight. No branch creation, no branch switch, no pull request, no force push.
Done	The checked-out branch is committed and pushed: git status --porcelain is empty and git rev-list --left-right --count origin/<current-branch>...HEAD prints 0 0.

Inputs

• Working-tree state (git status, git diff HEAD): required, gathered by the skill.
• Current branch and recent history (git branch --show-current, git log --oneline -10): required, gathered by the skill.
• Push-target state (git rev-list --left-right --count origin/<current-branch>...HEAD): required, gathered by the skill. NO_REMOTE_BRANCH means the local tracking ref is absent; step 5 observes the remote with git ls-remote --heads origin <current-branch> to decide whether the branch is new.
• Default branch (git rev-parse --abbrev-ref origin/HEAD, then git ls-remote --symref origin HEAD, then gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name' verified against git ls-remote --heads origin <default>): required as the preview base for a branch new to origin. When every resolver fails, the skill stops; a default branch is never guessed.
• Mode (current or commit-push-main): required, chosen by the invocation. commit-push-main is set when the human names the default branch as the push target; otherwise current.

Procedure

1. Gather context: run git status, git diff HEAD, git branch --show-current, git log --oneline -10, git remote, git rev-list --left-right --count origin/$(git branch --show-current)...HEAD 2>/dev/null || echo NO_REMOTE_BRANCH, and git rev-parse --abbrev-ref origin/HEAD 2>/dev/null || echo DEFAULT_BRANCH_UNRESOLVED. When git remote lists no origin, skip the resolution below; step 4 reports local-only. Otherwise, strip the origin/ prefix from the default branch; treat DEFAULT_BRANCH_UNRESOLVED or bare HEAD as unresolved. When unresolved, run git ls-remote --symref origin HEAD and take the branch named by the first ref: refs/heads/<name> line. When that fails too, run gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name' and accept its name only when git ls-remote --heads origin <name> lists it. When every resolver fails, report DEFAULT_BRANCH_UNRESOLVED and stop; never guess. Done when: tree state, branch, recent history, push-target counts, and default branch are known, or the skill has stopped.
2. Classify the branch state. Done when: the state is classified and the skill continues or stops.
   • commit-push-main mode with a mismatch (checked-out branch is not the resolved default branch, or HEAD is detached): report the mismatch and stop. This mode pushes only the default branch.
   • Detached HEAD (empty branch name): there is no branch ref to push. Report that this skill pushes only the checked-out branch and stop. commit-push-pr in no-PR mode creates a feature branch when one is wanted.
   • commit-push-main mode preflight, before any routing below: on NO_REMOTE_BRANCH, verify with git ls-remote --heads origin <default> — empty output means report that origin/<default> does not exist and stop, because this mode never creates the remote default branch; a failed call means the remote cannot be observed: report and stop; non-empty means materialize the ref with git fetch --no-tags origin refs/heads/<default>:refs/remotes/origin/<default> and read the counts again. With an existing tracking ref, materialize the same refspec first. When either fetch fails, report and stop before any commit. Without origin, report local-only and stop, because the default branch cannot be verified without a remote.
   • Nothing to do (clean tree and zero on the right side of the push-target counts): report and stop.
   • Clean tree with commits ahead of the push target: skip to step 5; in current mode a clean tree with NO_REMOTE_BRANCH also skips to step 5 as a branch new to origin. Otherwise continue, including a dirty tree: with no origin, step 4 reports local-only; otherwise step 3 authors the commits. Only a clean tree skips the commit step.
3. Author the commits with commit. Its message conventions, atomicity rules, and staging discipline apply. Do not restate them here. Its default-branch auto-branching does not apply: invocation on the checked-out branch is explicit authorization to commit on it. Done when: commit reports the working tree committed, or reports nothing to commit.
4. Detect the remote with git remote. If no origin remote exists (empty output, or other remotes but none named origin), do not push and do not add or guess a remote. Report local-only and stop. Done when: origin is confirmed present, or the local-only result is reported.
5. Preview the push and wait for explicit human approval. Name the target origin/<current-branch> and observe the remote: git ls-remote --heads origin <current-branch>. Non-empty output (branch exists on origin): refresh the tracking tip with git fetch --no-tags origin refs/heads/<current-branch>:refs/remotes/origin/<current-branch>; when the fetch fails, report and stop without pushing. List git log --oneline origin/<current-branch>..HEAD. When the left count is non-zero, the remote holds commits HEAD lacks; name them in the preview, because the push will be rejected until they are integrated. Empty output (branch new to origin): in commit-push-main mode this means the remote default branch does not exist: report and stop without pushing, even when a stale local tracking ref exists, because this mode never creates the remote default branch. Otherwise say so, then list the full commit range git log --oneline origin/<default>..HEAD, materializing the base first with git fetch --no-tags origin refs/heads/<default>:refs/remotes/origin/<default>; when that fetch fails and no local origin/<default> exists, report and stop without pushing, never falling back to an unanchored or truncated listing. A failed ls-remote call means the remote cannot be observed: report and stop without pushing. The push always targets origin, even when the configured upstream points elsewhere. Show the target and the commit list, then wait for the human to approve the exact mutation set (platform blocking question tool, chat fallback). On no answer or refusal, stop with nothing pushed. On approval, push with git push -u origin HEAD. Never force-push. Done when: the push is accepted, or the rejection or a stop is reported.
6. Verify: git status --porcelain is empty and git rev-list --left-right --count origin/<current-branch>...HEAD prints 0 0. Done when: both read clean, or the residue is reported.

Failure and recovery

• Detached HEAD: report and stop. No commit is created. Suggest commit-push-pr in no-PR mode for a feature branch.
• commit-push-main mode with a mismatch (checked-out branch is not the resolved default branch, or HEAD is detached): report the mismatch and stop. No commit is created.
• Nothing to do: report and stop. No mutation occurs.
• commit-push-main mode with the remote default branch found absent — at the step 2 preflight (NO_REMOTE_BRANCH and git ls-remote --heads origin <default> is empty) or at the step 5 preview (git ls-remote --heads origin <current-branch> returns empty despite a local tracking ref): report that origin/<default> does not exist and stop. This mode never creates the remote default branch.
• No origin remote: report local-only; in current mode name the unpushed commits. Never add, invent, or guess a remote. In commit-push-main mode this stops before any commit is created.
• Default branch unresolved after origin/HEAD, git ls-remote --symref origin HEAD, and verified gh: report and stop. A branch new to origin has no honest preview base without it. Never guess a default branch.
• No fetched base for a new-branch preview (fetch of <default> failed and origin/<default> is absent): report and stop before the push. The commit set is never previewed from HEAD alone or truncated.
• Tracking-tip refresh fails before an existing-branch preview: report and stop without pushing.
• Push rejected on a diverged remote branch: report the rejection and the counts from git rev-list --left-right --count origin/<current-branch>...HEAD. Leave resolution to the user. Never force-push.
• Verification residue (non-empty git status --porcelain, or counts other than 0 0): report the uncommitted files or unpushed commits. Do not claim done.

Output

The committed working tree on the checked-out branch, one push to origin/<current-branch> (the verified origin/<default> in commit-push-main mode), and a report naming the branch, the pushed commit hashes and subjects, and the verification result. When no origin remote exists, a local-only report naming the commits left unpushed.