A guide for writing commit messages that follow Conventional Commits, a standard format such as `fix: correct login error` that describes the kind of change made.

Use it when reviewing code changes and creating commit messages with types, scopes, descriptions, bodies, and breaking-change notes.

It makes a project's history easier to scan and helps tools identify fixes, features, and breaking changes consistently.

commit — Skill for Claude Code by skilluse/skilluse

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 skilluse/skilluse --skill commit

Clone the repo

git clone --depth 1 https://github.com/skilluse/skilluse

Made for: Claude Code.

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/skilluse/skilluse/commit/github.svg)](https://agentmods.dev/skills/skilluse/skilluse/commit)

Your own site

<a href="https://agentmods.dev/skills/skilluse/skilluse/commit"><img src="https://agentmods.dev/badge/skills/skilluse/skilluse/commit/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/skilluse/skilluse/commit"><img src="https://agentmods.dev/badge/skills/skilluse/skilluse/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 981 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 92% copy Near-identical to another mod 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.00032	$0.00981
Opus 5.5	$0.00013	$0.00392
Sonnet 5.5	$0.00006	$0.00196
Haiku 4.5	$0.00003	$0.00098

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

Security

Grade A, and why

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

Origin

This is a copy

92% identical to conventional-commit — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/commit/SKILL.md · 137 lines

How it starts

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

Conventional Commits Generator

Generate commit messages following the Conventional Commits 1.0.0 specification.

Commit Message Structure

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Instructions

When the user asks to commit changes:

Analyze the changes by running:
- git status to see all modified/added/deleted files
- git diff --staged to see staged changes
- git diff to see unstaged changes
- git log -5 --oneline to match the repository's commit style

Determine the commit type (REQUIRED):

Type	Description	SemVer
`feat`	New feature	MINOR
`fix`	Bug fix	PATCH
`docs`	Documentation only	-
`style`	Formatting, no code change	-
`refactor`	Code change, no feature/fix	-
`perf`	Performance improvement	-
`test`	Adding/updating tests	-
`build`	Build system or dependencies	-
`ci`	CI configuration	-
`chore`	Other changes	-

Identify breaking changes:
- Append "!" after type/scope for breaking changes: "feat!:" or "feat(api)!:"
- Add "BREAKING CHANGE:" footer for detailed explanation
- Breaking changes trigger MAJOR version bump
Write the commit message:
- Description MUST immediately follow the colon and space
- Description is a short summary in imperative mood
- Body MUST begin one blank line after description
- Footers MUST begin one blank line after body
Stage and commit:
- Stage relevant files with git add
- Create commit with the generated message
- Show git status after to confirm success
- DO NOT add any Claude Code references, co-author tags, or "Generated with" footers

Specification Rules

Type MUST be a noun (feat, fix, etc.)
Scope MUST be a noun in parentheses describing codebase section
Description MUST use imperative mood ("add" not "added")
Body is free-form, may have multiple paragraphs
Footer token MUST use - instead of spaces (except BREAKING CHANGE)
BREAKING CHANGE MUST be uppercase
NEVER include AI-generated markers, Claude Code references, or Co-Authored-By: Claude footers

Read the full file on GitHub · 137 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 · 137 lines · 32 tokens per session scan A 8ac000b7c8b1

Subscribe to this mod's changes

commit is a skill published in the GitHub repository skilluse/skilluse (55 stars, last pushed 7mo ago), licensed MIT. It adds 32 tokens to every session and 981 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to conventional-commit, differing in 6 lines, and is treated as a copy.

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

git-commit-writer

Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.

mergisi/awesome-openclaw-agents · 53 tokens