mcpField
G
git-commit-formatter

git-commit-formatter

github.com/rominiraniDevelopment60767 installsUpdated 18w ago
Repository

About git-commit-formatter

git-commit-formatter is a skill for writing Git commit messages that follow Conventional Commits. It guides type and optional scope selection, imperative descriptions, and breaking-change footers.

Key features

  1. 01Follow Conventional Commits format
  2. 02Choose type based on changes
  3. 03Identify an optional scope
  4. 04Write descriptions in imperative mood
  5. 05Add breaking-change footers

Use cases

  1. 01Write a commit for a new feature
  2. 02Choose a type for a bug fix
  3. 03Format documentation or test commits
  4. 04Mark breaking changes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/rominirani/antigravity-skills --skill git-commit-formatter

After installing, type/git-commit-formatterin Claude Code to confirm it loaded.

Details

From the project README

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 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

Comments

Markdown supported