commit-and-push

To commit and push git changes in one step, the workflow delegates commit message composition to a dedicated commit skill, then safely pushes the current HEAD to its remote branch. It automatically checks upstream tracking and uses git push -u origin for first-time publishing.

Running a commit and push action with a clean working tree results in a no-op. It detects that nothing changed and avoids empty commits, preventing stale or unrelated local history from being pushed to the remote repository.

The automated git push workflow never force-pushes to the remote branch. It includes safety guardrails that stop on non-fast-forward rejection, prompting a rebase-based workflow to safely resolve divergent histories.

For a local branch with no upstream set, the workflow checks tracking existence via git rev-parse @{u} and falls back to git push -u origin <branch>. This establishes the remote tracking relationship during the first push.

The safest way to automate git commit and push is to group staged changes into a fresh commit, verify upstream tracking, and push without force. This approach avoids empty commits and handles non-fast-forward rejections by stopping for a manual rebase.