Git Commit Message Formatter skill for Claude and Codex
Three ready-to-paste commit messages written from your diff in the team's convention, each with a precise subject line, a body that explains why, and the…
Install it once and Claude or Codex runs it for you. When your request matches, your AI loads the skill, asks for anything it is missing, and works through the template itself. Prefer to fill it in by hand? See the full prompt template.
Download the skill (.zip) · View SKILL.md
When it is used
Use when a diff or change needs a commit message in Conventional Commits or another house style, with the right type, scope, and footers. Do not use for writing pull request descriptions, release notes, or changelogs. Related topics: coding, git, utility.
What it will ask you for
- Diff or description of the change (longer free text)
- Convention (choose one: Conventional Commits (feat/fix/chore), Angular Style, Simple/Brief, Descriptive/Long)
- Ticket or issue number (free text, e.g. "PROJ-123 or leave blank")
- Impact of the change (choose any: Breaking Change, UI Update, Database Migration, Performance Fix, Security Fix, Dependency Update)
- Bulleted body (choose one: Yes, No)
How it works
- Identify the single behaviour change in the diff and decide whether it should be one commit or split, so the type and scope are unambiguous.
- Write an imperative subject line of 50 characters or fewer with no trailing full stop, in the convention's type and scope format.
- Draft the body around the reason and the consequence of the change, bulleted when requested, with nothing that merely restates the diff.
- Place the ticket reference and any BREAKING CHANGE footer where the convention expects them, adding a migration note for breaking changes.
- Present three variants of increasing length and name the one that matches the size of the change.
What you get
Three commit messages in fenced blocks, from subject only to subject with body and footers, followed by one line recommending which to use.
What it watches out for
- Describing what the code does now instead of what the change did, which makes the message useless in git blame.
- Tagging a mixed diff as feat when the user-visible part is a fix, so the changelog puts it under the wrong heading.
- Omitting the BREAKING CHANGE footer when Breaking Change was selected as an impact, which hides the change from semantic-release tooling.
How to install
Claude.ai and the Claude desktop app
- Download the skill .zip.
- Open Settings, then Capabilities, and find Skills.
- Choose Upload skill and select the .zip.
- Ask Claude for help with the task. It loads the skill when your request matches.
Claude Code
- Download the skill .zip.
- Unzip it into ~/.claude/skills/ (or .claude/skills/ inside a project).
- Start a new session. Claude Code loads the skill when your request matches.
Codex
- Download the skill .zip.
- Unzip it into ~/.agents/skills/ (or .agents/skills/ inside a project).
- Codex picks it up on its own. Type $ and the skill name to use it, or just ask for the task.
Cursor
- Download the Cursor rule (.mdc).
- Save it in .cursor/rules/ inside your project.
- Cursor's agent applies the rule when your request matches its description.
AGENTS.md (Codex, Cursor, and other coding agents)
- Copy the AGENTS.md section.
- Paste it into AGENTS.md at the root of your repository, creating the file if needed.
- Coding agents that read AGENTS.md follow it when your request fits.