What is git-conventional-commits?

A guide for writing Git commit messages that follow Conventional Commits, a standard format used by tools to understand the type and scope of changes. It also covers naming branches and commits.

It helps choose commit types, scopes, subjects, bodies, and footers for completed features, fixes, refactors, and other repository changes.

It removes uncertainty when naming commits and makes the project history easier for people and release tools to read. Consistent messages can support automatic changelogs and version updates.

How aigengame/cli-agentic-workflow configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to aigengame/cli-agentic-workflow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/aigengame/cli-agentic-workflow/main/.agents/skills/git-conventional-commits/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/aigengame/cli-agentic-workflow

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/aigengame/cli-agentic-workflow/git-conventional-commits/github.svg)](https://agentmods.dev/skills/aigengame/cli-agentic-workflow/git-conventional-commits)

Your own site

<a href="https://agentmods.dev/skills/aigengame/cli-agentic-workflow/git-conventional-commits"><img src="https://agentmods.dev/badge/skills/aigengame/cli-agentic-workflow/git-conventional-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/aigengame/cli-agentic-workflow/git-conventional-commits"><img src="https://agentmods.dev/badge/skills/aigengame/cli-agentic-workflow/git-conventional-commits.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 889 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.00035	$0.00889
Opus 5.5	$0.00014	$0.00356
Sonnet 5.5	$0.00007	$0.00178
Haiku 4.5	$0.00003	$0.00089

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

Security

Grade A, and why

git-conventional-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 2mo 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.

.agents/skills/git-conventional-commits/SKILL.md · 85 lines

How it starts

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

This skill enables the code agent to formulate precise, standard-compliant Git commit messages and branch names based on the Conventional Commits 1.0.0 specification. Adhering to this standard allows automated tools to parse commit histories, bump semantic versions (Major/Minor/Patch) accurately, and generate clean changelogs.

Requirements & Triggers

Trigger: Whenever the agent completes a task, implements a feature, fixes an issue, or refactors code and is ready to execute git commit.
Pre-requisite: Understand the scope of changes and know the associated GitHub Issue number (if any).

Guidelines & Rules

1. Commit Message Structure

Every commit message must strictly follow this structural pattern:

<type>(<scope>): <subject>

<body>

<footer>

(Required): Must be one of the structural keywords defining the change intent.
(Optional): A noun describing the affected section of the codebase enclosed in parentheses (e.g., auth, api, parser).
(Required): A succinct description of the change. Use imperative mood ("add" not "added"). No period . at the end.

2. Allowed Commit Types ( )

Type	Definition	SemVer Impact
`feat`	A new feature implemented in the codebase	Minor
`fix`	A bug fix implemented in the codebase	Patch
`docs`	Documentation only changes (e.g., markdown files)	None
`style`	Changes that do not affect the meaning of the code (white-space, formatting, etc.)	None
`refactor`	A code change that neither fixes a bug nor adds a feature	None
`perf`	A code change that improves performance	None
`test`	Adding missing tests or correcting existing tests	None
`build`	Changes that affect the build system or external dependencies	None
`ci`	Changes to CI configuration files and scripts	None
`chore`	Other changes that don't modify src or test files (e.g., .gitignore)	None

Read the full file on GitHub · 85 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.

2mo ago First seen · 85 lines · 35 tokens per session scan A 88125a16c801

Subscribe to this mod's changes

git-conventional-commits is a skill published in the GitHub repository aigengame/cli-agentic-workflow (20 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 889 once invoked, about $0.0001 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.

Commits Git and workflow agentic-workflows ai-agents cli workflow-orchestration

git-conventional-commits next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
git-conventional-commitsaigengame/cli-agentic-workflow	Skill	20	4mo ago	MIT	A	35	Claude Code, Codex
autofix-prQwenLM/qwen-code	Skill	29k	yesterday	Apache-2.0	A	141	Claude Code
cw-landHmbown/Codewhale	Skill	41k	1mo ago	MIT	A	44	Claude Code, Codex
git-commitUfoMiao/zcf	Skill	6.1k	8d ago	MIT	A	41	Claude Code
git-mastercode-yeongyu/lazycodex	Skill	3.9k	yesterday	MIT	A	93	Codex
atmos-gitcloudposse/atmos	Skill	1.4k	yesterday	Apache-2.0	A	82	Claude Code
conventional-committermio-sh/termio	Skill	785	4d ago	MIT	A	47	Claude Code, Codex

cli-agentic-workflow: Skill for Claude Code