git-commit-push

zc277584121/mygitplugin

Commit changes and push to origin without creating a PR

What is git-commit-push?

Automates git workflows by staging changes, creating commits with proper signoff, and pushing to origin. Use this when you need to commit work directly to a branch without opening a pull request.

Reviews staged changes using git status and git diff before committing
Stages files selectively to avoid including temporary or debug code
Creates signed commits with specified author and descriptive messages
Pushes commits to origin on the specified or current branch
Optionally creates new branches for isolated work

How to install git-commit-push

npx skills add https://github.com/zc277584121/mygitplugin --skill git-commit-push

Prerequisites

Git installed and configured locally
Repository already cloned and checked out
User has push access to the target branch

Claude Code

Cursor

Windsurf

Cline

How to use git-commit-push

1.Review pending changes with git status and git diff to verify what will be committed
2.Optionally create a new branch with git checkout -b <branch-name> or use current branch
3.Stage relevant files individually using git add <file> (avoid git add -A or git add .)
4.Run the commit command with --signoff flag and a clear, concise commit message in English
5.Push the branch to origin with git push origin <branch-name>

Use cases

Good for

Committing bug fixes directly to a development branch
Pushing feature work to origin without PR overhead
Staging and committing refactoring changes with proper attribution
Pushing hotfixes to a release branch
Committing documentation updates directly to main

Who it's for

Developers working in repositories with direct-commit workflows
Teams using branch-based development without mandatory PR reviews
Engineers pushing to internal or staging branches

git-commit-push FAQ

Can I commit directly to the current branch?

Yes. The skill will skip branch creation if you prefer to commit to your current branch.

Why not use git add -A or git add .?

Selective staging prevents accidentally committing temporary files, debug code, or unrelated changes.

What should the commit message include?

A concise English description of the changes. Do not mention AI, Claude, LLM, or automatic generation.

Is the --signoff flag required?

Yes. All commits require --signoff with author set to Cheney Zhang <chen.zhang@zilliz.com>.

Does this create a pull request?

No. This skill commits and pushes directly to the branch without opening a PR.

Full instructions (SKILL.md)

Source of truth, from zc277584121/mygitplugin.

name: git-commit-push description: Commit changes and push to origin without creating a PR allowed-tools:

Bash

Git Commit & Push

提交改动并推送到 origin 远端，不创建 PR。

触发条件

当用户要求提交改动并 push（但不需要提 PR）时使用此 skill。

执行步骤

创建新分支：git checkout -b <branch-name>，分支名由用户指定或根据改动内容自动生成。如果用户希望直接在当前分支提交，则跳过此步。
Review 改动：先用 git status 和 git diff 自行检查所有改动，确保没有把临时文件、调试代码或不相关的文件混进来。
暂存文件：git add 相关改动文件。不要使用 git add -A 或 git add .，而是逐个添加相关文件。
提交改动：
```
git commit --signoff --author="Cheney Zhang <chen.zhang@zilliz.com>" -m "<commit message>"
```
- commit message 用英文编写，简洁描述改动内容。
- 绝对不要在 commit message 中提及 AI、Claude、LLM 或任何自动生成相关的字样。
推送分支：git push origin <branch-name>。