Git Commit Push
Let your coding agent commit only the right files, sign off, and push to origin when you do not want a pull request opened yet.
Overview
git-commit-push is an agent skill most often used in Ship (also Build) that commits reviewed changes with sign-off and pushes to origin without creating a PR.
Install
npx skills add https://github.com/zc277584121/mygitplugin --skill git-commit-pushWhat is this skill?
- 5-step workflow: optional branch, review, selective stage, signed commit, push to origin
- Inspects changes with git status and git diff before staging
- Stages files individually—explicitly avoids git add -A and git add .
- Signed commits with --signoff and English messages that omit AI/LLM attribution
- Skips PR creation; pushes only to origin on the target branch
- 5-step commit-and-push workflow
- Per-file git add (no git add -A)
Adoption & trust: 381 installs on skills.sh; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want changes on the remote quickly but keep sloppy staging, debug files, or AI-tagged commit messages out of your history.
Who is it for?
Solo builders batching agent edits who need selective git add, sign-off commits, and push-only handoff to origin.
Skip if: Teams that require pull requests, custom commit authors per repo without editing the skill, or fully automated git add -A workflows.
When should I use this skill?
When the user asks to commit changes and push to origin without creating a PR.
What do I get? / Deliverables
You get a signed commit on the intended branch and an origin push, with no PR opened until you ask for one separately.
- Signed commit on target branch
- Pushed branch on origin
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Commit-and-push discipline sits on the shipping path right before collaboration and release gates, even though you may run it during active build work. Review-oriented git steps (status, diff, selective add) match the ship/review shelf where you harden what leaves your machine.
Where it fits
Push a backend fix branch to origin so preview deploys run without opening a PR yet.
Run status and diff, stage only source files, then sign-off commit before sharing the branch.
Land a hotfix commit and push to origin when incident response skips formal PR flow.
How it compares
Use instead of ad-hoc agent git commands when you want a fixed review-and-stage checklist rather than a generic “commit everything” prompt.
Common Questions / FAQ
Who is git-commit-push for?
Indie and solo developers using shell-capable coding agents who routinely commit and push without opening PRs.
When should I use git-commit-push?
During build when syncing feature branches to origin for CI, and during ship when you want a last diff review before push—any time the user asks to commit and push but not open a PR.
Is git-commit-push safe to install?
It runs git and Bash against your repository; review the Security Audits panel on this page and confirm branch, author, and remote before executing pushes.
SKILL.md
READMESKILL.md - Git Commit Push
# Git Commit & Push 提交改动并推送到 origin 远端，不创建 PR。 ## 触发条件 当用户要求提交改动并 push（但不需要提 PR）时使用此 skill。 ## 执行步骤 1. **创建新分支**：`git checkout -b <branch-name>`，分支名由用户指定或根据改动内容自动生成。如果用户希望直接在当前分支提交，则跳过此步。 2. **Review 改动**：先用 `git status` 和 `git diff` 自行检查所有改动，确保没有把临时文件、调试代码或不相关的文件混进来。 3. **暂存文件**：`git add` 相关改动文件。不要使用 `git add -A` 或 `git add .`，而是逐个添加相关文件。 4. **提交改动**： ```bash git commit --signoff --author="Cheney Zhang <chen.zhang@zilliz.com>" -m "<commit message>" ``` - commit message 用英文编写，简洁描述改动内容。 - **绝对不要**在 commit message 中提及 AI、Claude、LLM 或任何自动生成相关的字样。 5. **推送分支**：`git push origin <branch-name>`。 ## 注意事项 - 提交前检查是否有未暂存的改动需要处理。 - 所有 commit 都需要 `--signoff`，作者为 "Cheney Zhang <chen.zhang@zilliz.com>"。 - commit message 中不能出现任何 AI 相关字样。