A set of rules for writing clear Git commit messages in a standard format, such as marking a change as a feature, fix, documentation update, or refactoring. Git is the tool developers use to track code changes.

Use it when creating commits to choose suitable prefixes, describe changes clearly, and mark breaking changes that require users to adjust their code.

It makes commit history consistent and helps tools determine the kind of change each commit represents.

git-commits — Skill for Claude Code by jpoutrin/product-forge

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add jpoutrin/product-forge --skill git-commits

Clone the repo

git clone --depth 1 https://github.com/jpoutrin/product-forge

Made for: Claude Code.

Or install git-workflow, the plugin that ships this one along with the rest of its 11 skills, 8 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jpoutrin/product-forge/git-commits/github.svg)](https://agentmods.dev/skills/jpoutrin/product-forge/git-commits)

Your own site

<a href="https://agentmods.dev/skills/jpoutrin/product-forge/git-commits"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/git-commits/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jpoutrin/product-forge/git-commits"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/git-commits.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 591 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00039	$0.00591
Opus 5.5	$0.00016	$0.00236
Sonnet 5.5	$0.00008	$0.00118
Haiku 4.5	$0.00004	$0.00059

Measured 1mo ago against content hash e79ed547eb69, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

git-commits scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/git-workflow/skills/git-commits/SKILL.md · 102 lines

How it starts

The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Git Commits Skill

This skill enforces git commit best practices and conventional commits format.

Conventional Commits Format

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Commit Types

Type	Description	Semver
`feat`	New feature	MINOR
`fix`	Bug fix	PATCH
`docs`	Documentation only	-
`style`	Formatting, no code change	-
`refactor`	Code restructuring	-
`perf`	Performance improvement	PATCH
`test`	Adding tests	-
`chore`	Maintenance tasks	-
`ci`	CI configuration	-
`build`	Build system changes	-

Examples

Feature

feat(auth): add OAuth2 login support

Implement OAuth2 flow with Google and GitHub providers.
Includes token refresh and secure storage.

Closes #123

Bug Fix

fix(api): handle null response in user endpoint

The /users endpoint crashed when the database returned null.
Added proper null checking and error response.

Breaking Change

feat(api)!: change response format for /users endpoint

BREAKING CHANGE: Response now returns array instead of object.
Migration guide available in docs/migrations/v2.md

Atomic Commits

Each commit should:

Represent ONE logical change
Be independently revertible
Pass all tests
Be complete (not "WIP")

Bad Example

git commit -m "Fix bugs and add features and update docs"

Good Example

git commit -m "fix(auth): prevent session timeout on refresh"
git commit -m "feat(dashboard): add export to CSV button"
git commit -m "docs(api): update authentication examples"

Commit Message Rules

Type is required and lowercase
Description starts lowercase, no period
Imperative mood: "add" not "added" or "adds"
First line under 72 characters
Body wraps at 72 characters
Breaking changes marked with ! or footer

Claude Code Commit Footer

When committing with Claude Code, include:

Read the full file on GitHub · 102 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 102 lines · 39 tokens per session scan A e79ed547eb69

Subscribe to this mod's changes

git-commits is a skill published in the GitHub repository jpoutrin/product-forge (16 stars, last pushed 7mo ago), licensed MIT. It adds 39 tokens to every session and 591 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Commits Git and workflow

create-pr

Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.

prisma/orm · 48 tokens

git-commit

Generate well-formatted git commit messages following conventional commit standards.

ThinkInAIXYZ/deepchat · 15 tokens

repo-sync

Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.

davidondrej/skills · 25 tokens

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

contributing

How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…

HugoRCD/evlog · 68 tokens

engineer-bot-ops

A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.

makecindy/cindy · 57 tokens