How do I install the Git Commit Push skill?

Run npx skillmds@latest add ainova-systems/git-commit-push in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Git Commit Push safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Commit Push?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Git Commit Push free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Git Commit Push?

ainova-systems (@ainova-systems) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Commit Push by ainova-systems — Agent Skill

Name: Git Commit Push
Author: ainova-systems

File contents

Commit and Push

Land the pending work as one verified, cleanly described commit. Invoke at milestones - one commit = one shippable-for-testing unit.

Steps

git branch --show-current - on a protected branch (default/integration), STOP; work happens on feature branches.
Run the gates: typecheck + lint always, tests scoped to the change (dev-run-tests). Failure - fix or report, never bypass.
Review the diff: git status --porcelain + git diff. Drop debug leftovers and accidental files. Stage selectively with git add <paths> - never blanket git add -A (it sweeps secrets and parallel-session work). Then run git-scan-secrets (diff scope): a live credential in what you are about to commit stops the commit until the value moves to the environment or secret store; one found elsewhere in the pending diff is reported, not swallowed, and does not block this commit.
One logical change per commit; unrelated edits split into separate commits. In spec-driven projects, tick the plan's ## Work steps boxes in the same commit as the code that earns them.
Message: one line, capital first letter, past tense, work-item id when the project uses them (Added export endpoint (FR-042)). An explicit argument overrides.
git commit, then git push (-u origin <branch> on first push). Remote moved - integrate per profile update_strategy, re-run gates, push again. Never force-push.

Verify

git log --oneline -1 shows the message; git status reports up to date with origin; gates were green on the pushed tree.

Scope / hand-off

Opening the PR - git-open-pr; the CI / verify / review rounds - git-finalize-pr; the outcome - git-complete-pr (or spec-execute Phase E in spec projects).

Constraints

Never weaken a gate to commit (dev-verification-gates); never --no-verify.

---name: git-commit-pushdescription: Commits pending work as one verified milestone and pushes it. Stops at the push - opening the pull request is git-open-pr.---# Commit and PushLand the pending work as one verified, cleanly described commit. Invoke at milestones - one commit = one shippable-for-testing unit.## Steps1. `git branch --show-current` - on a protected branch (default/integration), STOP; work happens on feature branches.2. Run the gates: typecheck + lint always, tests scoped to the change (`dev-run-tests`). Failure - fix or report, never bypass.3. Review the diff: `git status --porcelain` + `git diff`. Drop debug leftovers and accidental files. Stage selectively with `git add <paths>` - never blanket `git add -A` (it sweeps secrets and parallel-session work). Then run `git-scan-secrets` (`diff` scope): a live credential in what you are about to commit stops the commit until the value moves to the environment or secret store; one found elsewhere in the pending diff is reported, not swallowed, and does not block this commit.4. One logical change per commit; unrelated edits split into separate commits. In spec-driven projects, tick the plan's `## Work steps` boxes in the same commit as the code that earns them.5. Message: one line, capital first letter, past tense, work-item id when the project uses them (`Added export endpoint (FR-042)`). An explicit argument overrides.6. `git commit`, then `git push` (`-u origin <branch>` on first push). Remote moved - integrate per profile `update_strategy`, re-run gates, push again. Never force-push.## Verify- `git log --oneline -1` shows the message; `git status` reports up to date with origin; gates were green on the pushed tree.## Scope / hand-off- Opening the PR - `git-open-pr`; the CI / verify / review rounds - `git-finalize-pr`; the outcome - `git-complete-pr` (or `spec-execute` Phase E in spec projects).## Constraints- Never weaken a gate to commit (`dev-verification-gates`); never `--no-verify`.

Frequently asked questions

Git Commit Push