How do I install the Git Commit Formatter skill?

Run npx skillmds@latest add tomevault-io/git-commit-formatter-3 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Git Commit Formatter skill do?

Formats git commit messages according to Conventional Commits specification. Use this when the user asks to commit changes or write a commit message. Use when this capability is needed. It is listed under Coding & Dev Tools on SkillMD.

Is Git Commit Formatter safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Commit Formatter?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Git Commit Formatter free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Git Commit Formatter?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Commit Formatter by tomevault-io

Name: Git Commit Formatter
Author: tomevault-io

File contents

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

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

Frequently asked questions

Git Commit Formatter