Index of every page on this site: llms.txt
All skills
github avatar

/git-commit

@f10fdb8 official
by githubgithub/awesome-copilot41k stars
5,399
Run it yourself

Use this skill when the user wants to make a Git commit or split changes into more than one commit. Also use it when the user types "/commit" or asks for a conventional commit. The skill examines the diff, stages the related files, writes a Conventional Commits message, and runs git commit. Do not use it when the user wants only a commit message and no commit. Do not use it to push, open a pull request, rebase, or change the commit history.

Use this Skill: https://skilld.dev/gh/github/awesome-copilot/git-commit

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈114 tokens for metadata: the name and description. ≈2k when used: this file.

Description uses 5.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈457 characters, or 5.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Git Commit with Conventional Commits

Make Git commits that follow the Conventional Commits 1.0.0 specification. Get the type, the scope, and the summary from the diff.

Message Format

<type>(<scope>): <summary>

<body>

<footer>
  • The scope, the body, and the footer are optional. Without a scope, write <type>: <summary>.
  • Write the summary in the imperative mood: "add", not "added" or "adds".
  • Keep the first line at 72 characters or less. Do not put a period at the end.
  • In the body, tell what changed and why.
  • Write each footer as Token: value or Token #value, for example Refs: #456 or Closes #123. Conventional Commits accepts the two forms, but Git reads only Token: value as a trailer. In a token, use - in place of a space.

Types

Conventional Commits defines only feat and fix. The other types come from the Angular convention (@commitlint/config-conventional). If the repository has its own list, use that list.

Type Use it for
feat A new feature
fix A bug fix
docs Documentation only
style Formatting only, with no change to the logic
refactor A code change that is not a feature or a fix
perf A performance improvement
test New or changed tests
build The build system or the dependencies
ci The CI configuration
chore Other maintenance
revert A revert of an earlier commit

Breaking Changes

Put ! before the colon, or add a BREAKING CHANGE: footer. Write the token in uppercase. BREAKING-CHANGE: is also correct.

feat(api)!: remove the v1 endpoints

BREAKING CHANGE: Clients must use the v2 endpoints.

Workflow

1. Read the repository rules

Find the commit rules before you write a message:

  • A commitlint configuration, for example commitlint.config.js or .commitlintrc.json.
  • CONTRIBUTING.md.
  • The recent messages: git log --oneline -10.

If a repository rule is different from this skill, use the repository rule.

2. Examine the changes

git status --porcelain
git diff --staged
git diff

If there are no changes, run the checks at the start of step 3. If they find MERGE_HEAD, continue. If not, tell the user what git status --long shows. Do not make an empty commit.

3. Stage the files

First, check for an operation in progress. Run each command alone. Do not chain them with &&. In a subdirectory, run every command in this step as git -C <root> .... git rev-parse --show-toplevel prints the root.

git rev-parse -q --verify --symbolic-full-name MERGE_HEAD
git rev-parse -q --verify --symbolic-full-name CHERRY_PICK_HEAD
git rev-parse -q --verify --symbolic-full-name REVERT_HEAD
git diff --name-only --diff-filter=U --no-relative
git status --long

A rev-parse command prints a ref name if its operation is in progress. If not, the command prints nothing and exits with status 1. The git diff command lists unmerged files. It finds conflicts that have no ref, for example from git stash pop. git status --long shows the other cases.

If an operation is in progress or there are unmerged files, do not unstage files. Do not split the commit. The index holds the result of the operation. If you unstage a file, Git drops the changes of the other side or removes a conflict entry.

  • Stop and tell the user if git status --long shows "rebase in progress", "You are in the middle of an am session", "Cherry-pick currently in progress", or "Revert currently in progress".
  • Run git status --porcelain=v2. A line that starts with u shows an unmerged file. You can resolve the file only if all these conditions are true:
    • The line starts with u UU N... or u AA N....
    • Each mode on the line is 100644, 100755, or 000000.
    • git diff --no-relative does not show Binary files differ for the file.
  • Ask the user how to resolve all other unmerged files. Git cannot find conflict markers in these files. git add --resolved and the checks below stage these files without a warning. Stage each of these files only after the user resolves it: git add -- <path>.
  • With Git 2.56 or later, stage the files that you can resolve with git add --resolved -- <paths>.
  • With older Git, check those files and stage them:
git diff --check -- path/to/file1 path/to/file2
git add -- path/to/file1 path/to/file2
  • Stage the files only if git diff --check finds no "leftover conflict marker" line. Ignore whitespace warnings from the other branch.
  • Then, with any Git version, run git diff --name-only --no-relative and git ls-files --others --exclude-standard. They list edits in other files. Skip the files that are still unmerged.
  • Show these paths to the user. Ask if they belong to the commit. Stage only the approved paths with git add -- <paths>.
  • Git quotes some paths, for example paths with non-ASCII characters. git add fails for a quoted path. Ask the user about these files.

If there is no operation and no unmerged file, put one logical change in each commit. If the staged files contain more than one change, first unstage the files of the other changes. Then stage the files for this change:

git reset -q -- path/to/other-file1 path/to/other-file2
git add -- path/to/file1 path/to/file2
git add -- '*.test.*'
git add -- src/components/
  • Put a glob in quotes. Without quotes, the shell expands the glob and does not find the files in subdirectories.
  • Do not use git add -p or git add -i. These commands wait for input from a person.
  • Examine the list of staged files with git diff --staged --name-only. Do not commit secrets, for example .env files, credentials.json, or private keys.

4. Write the message

Get each part from the diff:

  • Type: The kind of change.
  • Scope: The module or the area that the change affects.
  • Summary: What changed, in one line.

5. Commit

When step 3 finds MERGE_HEAD, CHERRY_PICK_HEAD, or REVERT_HEAD, run git commit --no-edit with no paths and no --cleanup option. This keeps the message that Git prepared. Do not write a new -m message. The message can keep the Conflicts: comment lines from Git. Do not remove them.

In all other cases:

Give each paragraph with a different -m option. Git puts a blank line between the paragraphs. This command works in Bash, PowerShell, and other shells.

git commit -m "feat(auth): add token refresh"
git commit -m "fix(parser): accept empty input" -m "An empty file caused a crash." -m "Closes: #123"

For a long message, write the message to a temporary file. Then run git commit -F <file>.

6. Make sure that the commit is correct

git log -1 --stat --first-parent
git status --porcelain

Safety Rules

  • Do not change the Git configuration.
  • Do not use --no-verify unless the user tells you to. Hooks can be in .git/hooks or in the Git configuration.
  • If a hook fails, Git does not make the commit. Fix the problem, stage the files again, and run the same git commit command again. Do not use --amend, because it changes the previous commit.
  • Do not change the commit history unless the user tells you to. Do not use git reset --hard, git rebase, or the experimental git history command.
  • Do not push unless the user tells you to. Do not force push to the default branch.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts12d5 checks · Risk SAFE
  • Gen Agent Trust Hub12d

    The skill automates Git commits following the Conventional Commits specification. It includes safety checks to avoid committing secrets and uses defensive command syntax to prevent misinterpretation of file paths. It is susceptible to indirect prompt injection if the code changes being committed contain malicious instructions designed to influence the commit message.

  • Socket13d

    No alerts

  • Snyk12d

    Risk: LOW · No issues

  • Runlayer8mo

    1 file scanned · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at f10fdb8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 weeks ago
All 1 allowed tools
shell(git:*)
Other metadata
compatibility
Requires Git. The `--resolved` option of `git add` requires Git 2.56 or later. Older versions use the fallback in step 3.
  • Git/VCS
  • conventional-commits
  • commit-messages
  • staging
  • bash
  • semantic-versioning

README badge

README badge for github/awesome-copilot/git-commit

Creates standardized git commits using the Conventional Commits specification by analyzing diffs to auto-detect type, scope, and generate messages. Supports intelligent file staging, interactive overrides, and breaking change footers for semantic versioning.

Generated from the current SKILL.md.

Does this skill auto-stage files or do I need to stage them manually?
The skill can intelligently stage files for logical grouping if nothing is already staged, but it analyzes whatever diff exists (staged or working tree) and prompts you before committing. You retain control over what gets staged.
What happens if my commit message doesn't follow Conventional Commits format?
The skill is designed to generate and enforce Conventional Commits format automatically by analyzing the diff and detecting the type, scope, and description. It will not create non-conforming messages.
Does this skill handle breaking changes?
Yes. The skill supports breaking changes via an exclamation mark after the type/scope (e.g., `feat!:`) or a BREAKING CHANGE footer in the commit body.
Will this skill run git hooks or skip validation?
The skill respects git hooks by default and will not skip them with --no-verify unless you explicitly request it. If a hook fails, it will prompt you to fix and create a new commit rather than amend.

Generated from the current SKILL.md. These answers refresh after source changes.