AGENTS-COLLECTION git-commit-formatter

Formats git commit messages according to Conventional Commits specification. Use this when the user asks to commit changes or write a commit message.

install

source · Clone the upstream repo

git clone https://github.com/mk-knight23/AGENTS-COLLECTION

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/mk-knight23/AGENTS-COLLECTION "$T" && mkdir -p ~/.claude/skills && cp -r "$T/AGENTS/ANTIGRAVITY/SKILLS/GIT-COMMIT-FORMATTER" ~/.claude/skills/mk-knight23-agents-collection-git-commit-formatter && rm -rf "$T"

manifest: AGENTS/ANTIGRAVITY/SKILLS/GIT-COMMIT-FORMATTER/SKILL.md

source content

Git Commit Formatter Skill

When writing a git commit message, you MUST follow the Conventional Commits specification.

Format

<type>[optional scope]: <description>

Allowed Types

feat: A new feature
fix: A bug fix
docs: Documentation only changes
style: Changes that do not affect the meaning of the code (white-space, formatting, etc)
refactor: A code change that neither fixes a bug nor adds a feature
perf: A code change that improves performance
test: Adding missing tests or correcting existing tests
chore: Changes to the build process or auxiliary tools and libraries such as documentation generation

Instructions

Analyze the changes to determine the primary
```
type
```
.
Identify the
```
scope
```
if applicable (e.g., specific component or file).
Write a concise
```
description
```
in imperative mood (e.g., "add feature" not "added feature").
If there are breaking changes, add a footer starting with
```
BREAKING CHANGE:
```
.

Example

feat(auth): implement login with google