commit

What it does and when to use it

Stage, commit, and push changes to the current branch. Use when asked to commit, push, or create a commit for the current task.

How it works

1. Gotchas

---
name: commit
description: Stage, commit, and push changes to the current branch. Use when asked to commit, push, or create a commit for the current task.
---

# Commit and Push Skill

1. Stage only files related to the current task
2. Run `git commit --no-verify` if pre-commit hooks fail on unrelated issues
3. Push to the current branch
4. Report the commit hash and branch name

NOTE: This repo uses Azure DevOps. For PRs use `az repos pr create`.
NOTE: The `commit-msg` hook strips `Co-Authored-By` trailers so commits appear as sole-author.

---

## Gotchas

- **`git commit --no-verify` bypasses pre-commit hook** — logged in reflog but easy to forget. A CI check that fails on no-verify trailers prevents drift.
- **`commit-msg` hook transforms the message AFTER the editor closes** — verify the final state with `git show -s --format=%B`, not the editor draft.
- **Azure DevOps strips `Co-Authored-By` server-side** — local commits show co-author; PR display doesn't. Test what shows in the PR UI before assuming attribution worked.
- **`git commit` on a detached HEAD creates an orphan** — `git checkout main` loses it unless you branch first. Reflog recovers but only for 30 days.
- **Trailing whitespace in commit messages**: some hooks normalize, some preserve. Format-checks comparing raw vs normalized fail confusingly.

Versions

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version ca3c73ef22bd (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

• 90commit-push-current
  Use when a human explicitly asks to commit and push to the checked-out branch with no branch creation and no pull request. Not for the default branch: use commit-push-main; not for a pull request: use commit-push-pr.
• 90commit-push-main
  Use when a human explicitly asks to commit and push directly to the default branch, with no feature branch and no pull request. Not for another checked-out branch: use commit-push-current.
• 100commit-push-pr
  Commit current changes, push to remote, and create or update a pull request. Use when the user wants to commit and create a PR, push changes and open a pull request, or ship their current work as a PR.
• 90git-commit-push
  Commit and push repository changes safely. Use when user asks to commit, push, or verify and push current changes.
• 90commit-push-current
  Use when a human asks to commit and push, not publish, the checked-out branch, including directly to the default branch, with no branch creation and no pull request. Not for a feature branch off the default: use commit-push-pr in its no-PR mode.
• 100commit-push
  Review, commit, and push local changes through the current branch's configured upstream. Use when you want to ship a deliberate commit without assuming a particular remote.