Git Commit Pr
- 2.3k installs
- Updated April 27, 2026
- zc277584121/mygitplugin
How do I commit my changes and create a pull request to an upstream repository with proper branch isolation, selective staging, signed commits, and clean PR metadata?
About
Automates the full Git workflow for committing changes and creating pull requests to official upstream repositories. Developers invoke this when ready to submit work: it creates a feature branch, reviews staged changes via git status/diff, selectively stages files, signs commits with author metadata, pushes to origin, and uses gh CLI to open a PR with customizable title and description. The skill includes safeguards against accidental commits of temp/debug files and enforces English-only, AI-attribution-free commit messages and PR text to maintain professional repository history.
- Guided branch creation with user-specified or auto-generated branch names
- Pre-commit review via git status and git diff to catch unintended files before staging
- Selective file staging (avoids git add -A/-. wildcards) to prevent accidental inclusions
- Signed commits with configurable author and structured English commit messages
- Integrated PR creation via gh CLI with title and body templates, plus optional merge and cleanup for users with merge pe
Git Commit Pr by the numbers
- 2,343 all-time installs (skills.sh)
- +216 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #34 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Security screen: CRITICAL risk (skills.sh audit)
- Data as of Aug 4, 2026 (Skillselion catalog sync)
git-commit-pr capabilities & compatibility
- Capabilities
- branch creation and checkout · diff review and staging control · signed commit generation · github pr creation via gh cli · upstream merge and cleanup (conditional)
- Use cases
- code review
- Platforms
- macOS · Linux · Windows · WSL
- Runs
- Runs locally
- Pricing
- Free
What git-commit-pr says it does
gh pr create --repo <official-owner/repo> --title "<PR title>" --body "<PR description>"
npx skills add https://github.com/zc277584121/mygitplugin --skill git-commit-prAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2.3k |
|---|---|
| Security audit | 1 / 3 scanners passed |
| Last updated | April 27, 2026 |
| Repository | zc277584121/mygitplugin ↗ |
What it does
Automate branch creation, file staging, commit signing, and pull request submission to upstream repositories.
Who is it for?
Teams using GitHub/upstream workflows who need deterministic branch creation, selective staging, and enforced commit/PR hygiene before pushing to official repositories.
Skip if: Direct main-branch commits, force-push scenarios, or workflows without upstream repository remotes.
When should I use this skill?
User requests to commit changes and create a pull request to the official upstream repository.
What you get
Developer submits a signed, reviewed commit on a feature branch with an open pull request ready for upstream maintainer review, with no temporary files, debug code, or AI attribution text.
- Feature branch created and pushed to origin
- Signed commit(s) with clean English commit message
- Pull request opened on official repository with title and description
By the numbers
- 7-step workflow: branch, review, stage, commit, push, create PR, optional merge/cleanup
- Enforces selective file staging (no wildcard adds)
- Requires signed commits with author metadata
Files
Git Commit & PR
提交改动并向 official（上游）仓库创建 Pull Request。
触发条件
当用户要求提交改动并给原始仓库（official）提 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>。
6. 创建 PR：
gh pr create --repo <official-owner/repo> --title "<PR title>" --body "<PR description>"- PR 标题和描述用英文编写。
- 绝对不要在 PR 标题或描述中提及 AI、Claude、LLM 或任何自动生成相关的字样。
- 不要添加
Co-Authored-By之类的 AI 相关标记。
7. 如果用户有合并权限且要求合并：
- Review PR 并合并。
- 切回主分支（main 或 master）。
- 同步上游：
git fetch official && git reset --hard official/<main-branch>。 - 删除本地临时分支：
git branch -d <branch-name>。 - 删除远端临时分支：
git push origin --delete <branch-name>。
注意事项
- 先确认
officialremote 存在，如果不存在则提示用户先配置。 - 提交前检查是否有未暂存的改动需要处理。
- 所有对外可见的文本（commit message、PR 标题/描述）都不能出现任何 AI 相关字样。
Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148How it compares
Choose git-commit-pr over generic commit skills when upstream sign-off, selective staging, and AI-free commit message rules are mandatory.
FAQ
Will the skill commit all my changes?
No. The skill reviews diffs, selectively stages only relevant files (via individual git add calls, never -A or .), and explicitly excludes temp/debug files to prevent accidental commits.
What commit metadata is included?
Commits are signed with --signoff and include author name and email. AI, Claude, LLM, and auto-generation references are strictly prohibited in commit messages and PR text per repository hygiene rules.
Can the skill merge the PR automatically?
Only if the user has merge permissions and explicitly requests it. The skill then reviews, merges, syncs with upstream, and cleans up local and remote branches.
Is Git Commit Pr safe to install?
skills.sh reports 1 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.