GI

git-commit-formatter

Auto-formatting for git commit messages using Conventional Commits.

Install

mkdir -p .claude/skills/git-commit-formatter && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/9690" && unzip -o skill.zip -d .claude/skills/git-commit-formatter && rm skill.zip

Installs to .claude/skills/git-commit-formatter

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Formats git commit messages according to Conventional Commits specification. Use this when the user asks to commit changes or write a commit message.
149 chars✓ has a “when” trigger
Beginner

Key capabilities

  • Commit message formatting
  • Conventional Commits enforcement
  • Breaking change documentation

How it works

Analyzes changes to generate messages following Conventional Commits specification.

Inputs & outputs

You give it
Code changes
You get back
Formatted commit message

When to use git-commit-formatter

  • Format commit messages
  • Ensure standard commit history
  • Generate breaking change notes

About this skill

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

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

Example feat(auth): implement login with google

When not to use it

  • Projects without commit standards

Prerequisites

Git

Limitations

  • Requires Conventional Commits standard

How it compares

Standardizes commit history for automated tooling and readability.

Compared to similar skills

git-commit-formatter side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
git-commit-formatter (this skill)04moNo flagsBeginner
resolve-conflicts818moReviewIntermediate
dependency-upgrade265moReviewIntermediate
openspec-onboard106moReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry