What is conventional-commit?

A rule for writing Git commit messages in the Conventional Commits format, a shared structure that labels changes such as features, fixes, and documentation.

Use it whenever code changes need to be committed, including checking the changes and identifying breaking changes.

It keeps commit history consistent and makes the kind of change clear to people and tools reading it.

conventional-commit — Skill for Claude Code and Codex by termio-sh

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 termio-sh/termio --skill conventional-commit

Clone the repo

git clone --depth 1 https://github.com/termio-sh/termio

Made for: Claude Code, Codex.

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

Your own site

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

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

When invoked 994 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00047	$0.00994
Opus 5.5	$0.00019	$0.00398
Sonnet 5.5	$0.00009	$0.00199
Haiku 4.5	$0.00005	$0.00099

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

Security

Grade A, and why

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

Copies of this mod

1 near-identical copy found in the catalogue:

commit — 92% identical, 6 lines differ

skills/conventional-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 Commit

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 · 47 tokens per session scan A 541c89c425fe

Subscribe to this mod's changes

conventional-commit is a skill published in the GitHub repository termio-sh/termio (544 stars, last pushed 4d ago), licensed MIT. It adds 47 tokens to every session and 994 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-08-30.

Claude Code Commits Git and workflow ade agentic ai-agents cli codex

teamserver-git

Commit, branch and push a Mendix project in git the way Studio Pro and Mendix Team Server expect — branches created on the server (not with git checkout -b), the mxmetadata commit note written with mxcli git note, and the notes ref pushed with the branch. Use before any git commit, branch, merge, rebase or push in a…

mendixlabs/mxcli · 108 tokens

git-flow-pr

Executes the full PR-driven development workflow: create an isolated feature branch from the current work, commit all staged changes, rebase cleanly onto the selected base branch (skipping any ancestor commits already merged), push the branch, and open a GitHub pull request linked to a related issue. Includes guidance…

soulcodex/agentic · 103 tokens

conventional-commit