Git commit skill for Claude Code: Conventional Commits from your diff

Source: github/awesome-copilot · Maintainer: community: GitHub awesome-copilot contributors · License: MIT · Checked: 24 October 2026

What is the git-commit skill?

The git-commit skill makes a coding agent turn your working changes into clean Git commits: it reads the diff, stages the files for one logical change, writes a Conventional Commits 1.0.0 message and runs git commit. It is for developers who let Claude Code, GitHub Copilot or Codex commit for them and want consistent history without hand-writing every message.

It lives in github/awesome-copilot, GitHub's MIT-licensed collection of community-contributed agents, instructions and skills. The README says these customizations "are sourced from third-party developers" and asks you to inspect them before installing. The skill's description opens: "Use this skill when the user wants to make a Git commit or split changes into more than one commit."

It is the most-installed skill from the repo on skills.sh, with about 47,200 installs on its skills.sh page (snapshot, 24 October 2026). The repo history shows it was added in January 2026 and rewritten in October 2026 to fix commands and support Git 2.56.

What does it do?

The skill is a single SKILL.md, with no scripts or reference files. Its frontmatter includes license: MIT, a compatibility note ("Requires Git") and an allowed-tools: shell(git:*) line.

It triggers when you ask to commit, split changes into several commits, type "/commit" or ask for a conventional commit. Its description also says when not to use it: when you only want a message, or to push, open a pull request, rebase or change history.

The workflow has six steps:

1. Read the repository rules. It looks for a commitlint config, CONTRIBUTING.md and the last 10 commit messages. "If a repository rule is different from this skill, use the repository rule."
2. Examine the changes with git status --porcelain, git diff --staged and git diff. If nothing changed, it tells you and makes no empty commit.
3. Stage one logical change. It unstages files that belong to other changes, then stages by path or quoted glob. It avoids git add -p and git add -i because they wait for a person, and checks the staged list for secrets such as .env files and private keys.
4. Write the message as <type>(<scope>): <summary>, taking type, scope and summary from the diff.
5. Commit with one -m per paragraph, or git commit -F <file> for a long message.
6. Verify with git log -1 --stat and git status --porcelain.

The message rules are specific: imperative mood ("add", not "added"), a first line of 72 characters or less with no final period, and a body that says what changed and why. Breaking changes get a ! before the colon or a BREAKING CHANGE: footer.

The type list comes from the Angular convention, since Conventional Commits itself defines only feat and fix:

How do you install it?

The skills.sh page gives this command for the skills CLI; add -a claude-code to target Claude Code or -g for all projects:

npx skills add https://github.com/github/awesome-copilot --skill git-commit

GitHub CLI 2.90.0 and later has a gh skill command, described in GitHub's changelog post on managing agent skills. It can target Claude Code directly:

gh skill install github/awesome-copilot git-commit --agent claude-code --scope user

You can also copy the folder by hand, which the repo's skills index also suggests. In Claude Code, a personal skill lives in ~/.claude/skills/git-commit/ and a project skill in .claude/skills/git-commit/, per the Claude Code skills docs. GitHub Copilot reads project skills from .github/skills, .claude/skills or .agents/skills, according to GitHub's docs on agent skills. Codex and Cursor read the same SKILL.md format; see Codex skills and Cursor skills.

How do you use it?

In Claude Code, the folder name becomes the command, so type /git-commit, or just ask to commit and let the agent load it.

Example prompts (suggestions, not quotes from the repo):

• /git-commit
• Commit these changes. Split the auth fix and the README update into separate commits.
• Make a conventional commit for the staged files only. Scope it to the parser.
• I resolved the merge conflicts. Stage the resolved files and commit the merge.
• Commit this API change and mark it as breaking: we removed the v1 endpoints.

Requirements: Git, and a repository with changes. The compatibility note says git add --resolved needs Git 2.56 or later. Per the git add docs, that option stages conflict-resolved paths and refuses to stage anything if a path still has conflict markers; Git's 2.56.0 release notes list it as new. If your repo has a commitlint config, the skill follows it over its own type list.

Tips and limits

From the SKILL.md and repo, not from testing:

• It will not push or rewrite history on its own. The safety rules say not to push or change history (git reset --hard, git rebase, the experimental git history command) unless you ask, and not to force push to the default branch. If a hook fails, it fixes the problem and runs the same commit again instead of using --amend.
• It respects hooks. It won't use --no-verify unless you tell it to, and it doesn't change your Git config.
• The allowed-tools line may not apply in Claude Code. Claude Code's skills docs show entries like Bash(git commit *), which pre-approve tools only for the turn that invokes the skill. The skill's shell(git:*) uses a syntax those docs do not describe, so expect your permission settings to decide whether git commands need approval.
• Messages only? Use a prompt. For a message you'll paste yourself, the commit message prompts fit better, since this skill always commits.
• Security audits: Gen Agent Trust Hub, Socket and Snyk all showed Pass on skills.sh on 24 October 2026.

Under the MIT License you can copy and change the skill, for example to add your team's own types, as long as you keep the copyright notice.

Save it in your Kipt library

In Kipt, open Skills and paste the skill's GitHub folder link into the import box. Because awesome-copilot holds hundreds of skills, pasting the folder link rather than the repo link takes you straight to this one; a repo link shows a list to pick from. Your copy lives in your own private GitHub repo, where you can adjust the type table for your team, ready to install into Claude Code or Codex with npx skills add https://github.com/<you>/<repo>.git --all -g. Kipt is not affiliated with GitHub or awesome-copilot.

Similar skills

• Docker skill: the multi-stage-dockerfile skill from the same awesome-copilot repo.
• Using git worktrees skill: gives the agent an isolated branch and workspace before it builds.
• Code review skill: checks a diff against your standards before you commit it.
• Receiving code review skill: how an agent should act on review feedback.