How do I install the Git Commit Push skill?

Run npx skillmds@latest add chann/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?

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

Git Commit Push by chann — Agent Skill

Name: Git Commit Push
Author: chann

Git Commit Push

Use when the user asks to commit working-tree changes AND push to the remote. Trigger on phrases like "commit and push", "커밋하고 푸시해줘", "/git-commit-push", "$git-commit-push", or "push my commits". Runs the git-commit workflow, then `git push` (never `--force`). For commit-only use `git-commit`; for history rewrite use `git-commit-rewrite`.

chann 35692c2 3 files · 4.8 KB Updated Sep 17, 2026

File contents

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.

---name: git-commit-pushdescription: Use when the user asks to commit working-tree changes AND push to the remote. Trigger on phrases like "commit and push", "커밋하고 푸시해줘", "/git-commit-push", "$git-commit-push", or "push my commits". Runs the git-commit workflow, then `git push` (never `--force`). For commit-only use `git-commit`; for history rewrite use `git-commit-rewrite`.---# Git Commit + Push## OverviewVariant 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:```bashgit push```If the current branch has no upstream:```bashgit 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 FlagsSame 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.

Frequently asked questions