git-commit
Skill1 starsChanged 7 months agoMITView on GitHub
Create Git commit messages following Conventional Commits format with automatic type and scope detection. Use when asked to "commit changes", "create a commit", "write commit message", or when ready to commit staged code. Supports feat, fix, docs, refactor, test, build, ci, chore, and revert types with project-specific scope determination based on file paths and directory structure.
178 other projects use a version of this.
Adopted by
Most recently taken up by
- tsaol/awesome-claudetheir own version, first seen Nov 15, 2026
- avinashankur/skillstheir own version, first seen Nov 15, 2026
- liao666brant/skillstheir own version, first seen Nov 15, 2026
- FimawLLC/fimaw-skillstheir own version, first seen Nov 15, 2026
- Dimon94/dveritytheir own version, first seen Nov 15, 2026
- Dimon94/skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use git-pr, github-pr-create and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
klauswgSkillgit-pr
Prepare, review, publish, or update a complete GitHub pull request for the current repository, including local commit readiness, safe push strategy, semantic title validation, repository-native PR templates, issue linking, and checks verification. Use when the user asks to draft, create, submit, publish, open, or update a pull request. Always require the user to review and explicitly approve the exact final PR before any push or GitHub write.
Also in 11 projects that use this
mjun0812Skillgithub-pr-create
Pull Requestを作成するSkill。現在のbranchからpull requestを作成する。言語指定可能。 ユーザーが「PR作って」「pull request作成して」のように依頼したら使うこと。
Also in 3 projects that use this
klauswgSkillgit-issue
Prepare, review, create, or update evidence-based GitHub issues for the current repository with duplicate detection, repository-native templates, valid labels, and post-publication verification. Use when the user asks to draft, file, submit, publish, edit, or refine a GitHub issue, bug report, feature request, performance issue, or technical proposal. Always require the user to review and explicitly approve the exact final issue before any GitHub write.
Also in 3 projects that use this
gologo13Skillgit-push
Push current branch to origin and sync with remote updates; keywords: git, rebase. Use only on explicit request; before execution, review diffs and list impact scope.
Also in 6 projects that use this
GoogleSkillgithub-pr-review
Review a GitHub pull request and leave inline comments in a natural human reviewing voice, indistinguishable from comments typed by hand on the GitHub web UI. Deliberately bounded to defects a reader can settle by looking at the anchored line, rather than a deep audit, so every comment is cheap for the author to check. Scales to 2-20 comments by PR size, parallelises analysis across sub-agents, drafts for approval, then posts individually with human pacing. Use when the user says "review this PR", "review PR 123", pastes a github.com/.../pull/N link, or asks for comments on a pull request. Don't use for reviewing local uncommitted changes or a diff against a branch (use the `review` skill for that).
Also in 4 projects that use this
GitHubSkillmulti-stage-dockerfile
Create optimized multi-stage Dockerfiles for any language or framework
Also in 3 projects that use this
Other versions178 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 178
- github/awesome-copilot★ 41ksame name
- doocs/leetcode★ 37ksame name
- tisfeng/Easydict★ 15ksame name
- doocs/md★ 14ksame name
- spinabot/brigade★ 11ksame name
- PC2005-cloud/dsh-pet★ 5.9ksame name
- GitTools/GitVersion★ 3.1ksame name
- igorescodro/alkaa★ 1.6ksame name
- microsoft/hve-core★ 1.6ksame name
- mattmireles/gemma-tuner-multimodal★ 1.5ksame name
168 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- gh-default-branchSkill
- gh-prSkill
- git-branchSkill
- git-commitSkill
- gh-default-branchSkill
- gh-prSkill
- git-branchSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 8 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 137 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use this skill when:
- Distinctive: line 31
Check the staged files using git diff --staged --name-only.
- Distinctive: line 32
Ask user to stage changes if there are no staged files.
- Distinctive: line 35
type: must be selected from the following options:
- Distinctive: line 50
scope: should be determined based on the directory structure of the staged files.
- Very specific: line 52
If staged files are in .claude/ or .mcp.json, use claude
- Very specific: line 53
If staged files are in .github/, use github
- Distinctive: line 58
If staged files are in the root directory, do not set a scope
- Very specific: line 62
Important: NEVER include \n in the commit message.
- Distinctive: line 77
Important: Commit messages must be written in English.
- Distinctive: line 78
If there are staged changes, determine the commit message based only on the staged changes.
- Very specific: line 79
Always include Co-Authored-By information.
“Common” is measured: kept by at least 6 in 10 of the 137 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Git Commit Skill
This skill guides the creation of Git commit messages that follow the Conventional Commits format.
When to Use
Use this skill when:
- Code changes are completed and ready to be committed
- Need to create a commit message that adheres to project conventions
Commit Message Format
The commit message must follow this format:
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]Instructions
- Check the staged files using
git diff --staged --name-only. Ask user to stage changes if there are no staged files. - Determine the appropriate commit type based on the staged files.
type must be selected from the following options:
feat: New feature or change to existing functionalityfix: Bug fixdocs: Documentation-only changes (e.g., changes to*.mdfiles)refactor: Refactoring (code changes that neither fix a bug nor add a feature)perf: Performance improvementstest: Adding or modifying tests (e.g., changes to*.spec.*or*.spec.*.snapfiles)build: Changes affecting the build system or external dependenciesci: Changes to CI configuration files (e.g., changes within.github/actionsor.github/workflows)chore: Other changes (e.g., changes to*.json,*.config.mjs,*.config.cjs,*.config.js,*.config.ts,.gitignore,.gitattributes,.prettierignore,.prettier)revert: Reverting a previous commit
- Determine the appropriate scope based on the staged files and the project structure.
scope should be determined based on the directory structure of the staged files. For example:
- If staged files are in
.claude/or.mcp.json, useclaude - If staged files are in
.github/, usegithub - If staged files are in
.vscode/, usevscode - If staged files are in
apps/frontend/, usefrontend - If staged files are in
libs/frontend/feature-xxx, usefrontend-feature-xxx - If staged files are in
libs/utils/, useutils - If staged files are in the root directory, do not set a scope
- Craft a comprehensive and descriptive commit message strictly following the Conventional Commits format.
Important NEVER include \n in the commit message. Always use actual newlines to separate the subject, body, and footer.
Example:
git commit -m "feat(utils): update xxx function
- Add xxx logic in xxx function
- Implement unit tests for xxx function
Co-Authored-By: Copilot <175728472+Copilot@users.noreply.github.com>"Notes
- Important Commit messages must be written in English.
- If there are staged changes, determine the commit message based only on the staged changes.
- Always include
Co-Authored-Byinformation. The commit message must clearly indicate that it was created with Copilot.
References
- Commit message
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

