Git Commit

Automatically generates conventional commit messages by analyzing your actual git diff instead of making you write them manually. It detects the commit type (feat, fix, docs, etc.) and scope from the changed files, stages related changes together, and creates properly formatted semantic commits that follow the spec. Particularly handy when you've made a bunch of changes and need to break them into logical, well-described commits without thinking through the conventional commit format yourself. Also prevents you from accidentally committing secrets or using destructive git commands.

install copies · 90 days. Times the install command was copied on this site in the last 90 days, bots filtered.: 24
skills.sh installs: 48.4K
GitHub stars: 41K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add github/awesome-copilot --skill git-commit --agent claude-code

Installs into .claude/skills of the current project.

Files

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.

SKILL.md on GitHub