07-commit-conventions

Commit rules based on Conventional Commits, a standard format that describes the kind of change in each Git commit.

In plain words
What is it for?
Formatting feature, fix, and documentation commits, marking breaking changes, and setting the required author identity for AI commits.
Why use it?
They make commit history consistent and let release tools determine version changes from commit messages.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/tecnomanu/agent-rules-kit/07-commit-conventions
Clone the repo
git clone --depth 1 https://github.com/tecnomanu/agent-rules-kit

Made for: Cursor.

Per session 1,088 This file is loaded in full into every session.
When invoked 1,088 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.01088 $0.01088
Opus 5 $0.00544 $0.00544
Sonnet 5 $0.00218 $0.00218
Haiku 4.5 $0.00109 $0.00109

Measured 2d ago against content hash 6e81dd668d34, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

07-commit-conventions 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 2d 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.

.cursor/rules/07-commit-conventions.mdc · 157 lines

How it starts

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

Commit Conventions

Follow Conventional Commits with emojis and semantic-release automation.

Basic Format

<type>: <emoji> <description>

[optional body]

[optional footer]

Common Types

Type Emoji Impact Example
feat MINOR feat: ✨ add user authentication
fix 🐛 PATCH fix: 🐛 handle timeout error
docs 📝 None docs: 📝 update README
chore 🔧 None chore: 🔧 bump dependencies

Breaking Changes (MAJOR version)

For major version bumps, use BREAKING CHANGE footer:

✅ Correct:

feat: 🎉 redesign authentication system

BREAKING CHANGE: Token format changed, requires client updates

❌ Wrong:

# Don't use exclamation mark
feat!: ✨ breaking change

# Don't make super long single-line messages
feat: 🎉 very long message with breaking change info all in one line BREAKING CHANGE: xyz

Author Identity (MANDATORY)

ALWAYS use --author for AI commits:

AI Assistant Commits:

# For Claude/Sonnet
git commit --author="Agent AI <[email protected]>" -m "feat: ✨ add feature"

# For Cursor AI
git commit --author="Agent AI <[email protected]>" -m "fix: 🐛 resolve issue"

Human Developer Commits:

# Use normal identity (no --author needed)
git commit -m "feat: ✨ implement feature"

Key Rules

  1. Keep commits short: Title under 72 characters
  2. Use blank lines: Separate title from body/footer
  3. Always use --author: For AI-generated commits
  4. BREAKING CHANGE footer: For major version bumps
  5. English only: All commit messages in English

Language

All commits must be written in English, regardless of your native language. This ensures consistency throughout the project, as all code, documentation, and rules are maintained in English.

Commit Format

We follow the Conventional Commits specification with emojis:

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

  1. 2d ago First seen · 157 lines · 1,088 tokens per session scan A 6e81dd668d34

Subscribe to this mod's changes

07-commit-conventions is a cursor rule published in the GitHub repository tecnomanu/agent-rules-kit (35 stars, last pushed 11mo ago), licensed ISC. It adds 1,088 tokens to every session, about $0.0054 per session on Opus 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.