A set of rules for writing Git commit messages in the Conventional Commits format. The format labels changes such as new features, bug fixes, documentation, and breaking changes.

Writing commit messages with a type, optional area of the code, short description, and—when needed—details about breaking changes.

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

git-commit — Cursor rule by titanzero

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/titanzero/outlook-mcp/git-commit

Clone the repo

git clone --depth 1 https://github.com/titanzero/outlook-mcp

Made for: Cursor.

Per session 692 This file is loaded in full into every session.

When invoked 692 The same file — it is already loaded in full.

Security scan A 0 findings. Scan, not verified.

Origin fork From a forked repository.

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	$0.00692	$0.00692
Opus 5	$0.00346	$0.00346
Sonnet 5	$0.00138	$0.00138
Haiku 4.5	$0.00069	$0.00069

Measured yesterday against content hash 7cd707b8300a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

git-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 yesterday.

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/git-commit.mdc · 62 lines

How it starts

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

Git Commit Messages

Follow the Conventional Commits standard.

Format

<type>(<scope>): <description>

[optional body]

[optional footer(s)]

type (required): feat, fix, refactor, chore, docs, test, style, perf, ci, build
scope (optional): module affected — auth, email, calendar, folder, rules, config, utils
description: imperative mood, English, lowercase, no trailing period, max ~72 characters

Structural Elements

fix: patches a bug (correlates with PATCH in Semantic Versioning)
feat: introduces a new feature (correlates with MINOR in Semantic Versioning)
BREAKING CHANGE: a footer BREAKING CHANGE:, or a ! after the type/scope, introduces a breaking API change (correlates with MAJOR in Semantic Versioning); can be part of any type
Other types (build, chore, ci, docs, style, refactor, perf, test) are allowed and have no implicit SemVer effect unless they include a BREAKING CHANGE
Footers other than BREAKING CHANGE: <description> may be provided and follow git trailer format

Specification Rules

Commits MUST be prefixed with a type, followed by OPTIONAL scope, OPTIONAL !, and REQUIRED terminal colon and space
feat MUST be used when a commit adds a new feature; fix MUST be used for bug fixes
A scope MAY be provided after the type, surrounded by parenthesis, e.g. fix(parser):
A description MUST immediately follow the colon and space — short summary of code changes
A longer body MAY follow the description, separated by one blank line; free-form, any number of paragraphs
One or more footers MAY be provided one blank line after the body; each footer uses a word token followed by :<space> or <space># separator
Footer tokens MUST use - in place of whitespace (exception: BREAKING CHANGE)
Breaking changes MUST be indicated in the type/scope prefix (!) or as a BREAKING CHANGE: footer
Types are NOT case sensitive, except BREAKING CHANGE which MUST be uppercase
BREAKING-CHANGE is synonymous with BREAKING CHANGE when used as a footer token

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

yesterday First seen · 62 lines · 692 tokens per session scan A 7cd707b8300a

Subscribe to this mod's changes

git-commit is a cursor rule published in the GitHub repository titanzero/outlook-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 692 tokens to every session, about $0.0035 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.

Debugging Git and workflow Writing and docs

git-commit

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Git Commit Messages

Format

Structural Elements

Specification Rules

What this file has done since we first saw it

Other cursor rules, from other repositories

angular-20

dev-standard

typescript

coolify-ai-docs

python_lib

specs