
Git Commit Push
- 2.4k installs
- Updated April 27, 2026
- zc277584121/mygitplugin
Automated staging, committing with sign-off, and pushing of git changes to origin without PR creation.
About
Git Commit & Push automates the workflow of staging changes, committing with sign-off, and pushing to origin. Developers use it when they need to save work to a remote branch without opening a PR. The skill reviews diffs before staging, commits with author attribution and sign-off flag, and pushes the branch. It enforces selective file staging (not blanket add), English commit messages, and explicit author metadata per organizational policy.
- Reviews git diff and status before staging to catch unintended files
- Stages files selectively by name instead of blanket git add
- Commits with --signoff and fixed author (Cheney Zhang) metadata
- Pushes to origin on user-specified or auto-generated branch name
- Skips pull request creation; direct branch push only
Git Commit Push by the numbers
- 2,353 all-time installs (skills.sh)
- +218 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #33 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 4, 2026 (Skillselion catalog sync)
git-commit-push capabilities & compatibility
- Works with
- github · gitlab · bitbucket
- Platforms
- macOS · Linux · Windows
- Runs
- Runs locally
- Pricing
- Free
What git-commit-push says it does
Commit changes and push to origin without creating a PR
git commit --signoff --author="Cheney Zhang <chen.zhang@zilliz.com>" -m "<commit message>"
npx skills add https://github.com/zc277584121/mygitplugin --skill git-commit-pushAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2.4k |
|---|---|
| Security audit | 2 / 3 scanners passed |
| Last updated | April 27, 2026 |
| Repository | zc277584121/mygitplugin ↗ |
What it does
Commit staged changes and push to origin branch without creating a pull request.
Who is it for?
Developers pushing work-in-progress or feature branches without opening pull requests; enforcing commit signing and author standards.
Skip if: PR creation, interactive rebase, merge conflict resolution, or remote branch deletion.
When should I use this skill?
User requests commit and push without PR; new feature branch needed; changes ready for remote storage.
What you get
Changes are committed with mandatory sign-off, fixed author metadata, and pushed to origin in one workflow.
- New or updated branch on origin
- Signed commit with fixed author metadata
- Pushed remote state reflecting local changes
By the numbers
- Supports selective file staging (no blanket add)
- Enforces --signoff flag on all commits
Files
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. 提交改动:
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 相关字样。
Related skills
How it compares
Use git-commit-push instead of full PR skills when the goal is a reviewed signoff commit pushed directly to origin.
FAQ
Will this create a pull request?
No. This skill commits and pushes to origin only. No PR is created.
Can I specify the branch name?
Yes. You can provide a branch name or let the skill auto-generate one based on the changes.
What happens to untracked files?
The skill reviews diffs before staging and avoids adding unrelated or temporary files via blanket add commands.
Is Git Commit Push safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.