mcpField
G
git-commit-push

git-commit-push

github.com/channDevelopment051 installsUpdated 2d ago
Repository

About git-commit-push

git-commit-push is a skill for developers who want to commit changes and push them to a remote using an established workflow. It relies on the git-commit skill and stops if a push is rejected, without force-pushing.

Key features

  1. 01Follows the standard Git commit workflow
  2. 02Pushes after commits succeed
  3. 03Sets origin upstream for branches without one
  4. 04Stops and reports rejected pushes
  5. 05Avoids force pushes and skipped hooks

Use cases

  1. 01Committing inspected and grouped changes
  2. 02Pushing committed changes to a remote branch

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/chann/skills --skill git-commit-push

After installing, type/git-commit-pushin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlevals/evals.json

Details

From the project README

Git Commit + Push

Overview

Variant of the git-commit skill that runs the standard commit workflow, then pushes the resulting commits to the remote. Never uses --force or --force-with-lease.

Announce at start: "I'm using the git-commit-push skill to commit and push these changes."

Workflow

Before starting, Read the main git-commit SKILL.md at <plugin-root>/skills/git-commit/SKILL.md — the full default workflow (steps 1–5), the secrets check, the commit-plan template, and the Red Flags list all live there. The variant relies on those sections.

Then follow ## Workflow: /git-commit in the main SKILL.md exactly — steps 1–5 (inspect, group, plan, commit, summary). After every commit succeeds, push:

git push

If the current branch has no upstream:

git push -u origin "$(git branch --show-current)"

If the push is rejected (non-fast-forward), stop and surface the error — do not retry, do not auto-resolve, do not use --force or --force-with-lease. Tell the user to git pull --rebase (or equivalent) and re-push manually.

See the "Worked Example" under ## Workflow: /git-commit-push in the main SKILL.md.

Red Flags

Same Never/Always lists as the main <plugin-root>/skills/git-commit/SKILL.md. In particular:

  • Never git add . or git add -A — always explicit paths.
  • Never bypass hooks with --no-verify.
  • Never --force push, and only --force-with-lease after explicit user consent.
  • Never commit suspected secret files (.env*, *_rsa, *.pem, *.key, *.p12, credentials.*) without explicit override. The exact basename .env.example is a public template and is not suspected solely because it matches .env*; every other secret-path rule still applies.

Integration

Pairs with: code-review (or code-review-md for Markdown only) — run a review before committing. Called by: Manual user invocation only. Never auto-run during another skill's workflow.

Comments

Markdown supported