commit-message-format

A rule for writing Git commit messages in a standard format, such as `fix: correct login error` or `feat(api): add search`. A commit message records what a code change contains.

In plain words
What is it for?
Use it whenever creating commits, including an optional area, explanation, or footer when more context is needed.
Why use it?
It makes a project's history easier to scan and keeps descriptions of fixes, features, tests, documentation, and other changes consistent.

Cursor rule

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/holtwood/awesome-cursorrules-zh/commit-message-format
Clone the repo
git clone --depth 1 https://github.com/holtwood/awesome-cursorrules-zh
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 186 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00186
Opus 5 $0.00000 $0.00093
Sonnet 5 $0.00000 $0.00037
Haiku 4.5 $0.00000 $0.00019

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

Security

Grade A, and why

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

docs/rules/backend/elixir/guidelines/commit-message-format.mdc · 23 lines

What it actually says

  • 使用以下提交消息格式: <类型>[可选范围]: <描述>

    [可选正文]

    [可选页脚]

    其中:

    类型:以下之一:fix(修复)、feat(功能)、build(构建)、chore(杂务)、ci(持续集成)、docs(文档)、perf(性能)、refactor(重构)、revert(回滚)、style(样式)、test(测试)

    范围(可选):描述代码库某部分的名词(例如 fluxcd、deployment)。

    描述:用现在时态简要总结更改。

    正文(可选):对更改的更详细解释。

    页脚(可选):一个或多个按指定格式的页脚。

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 · 23 lines · 186 tokens per session scan A 156dab1108d2

Subscribe to this mod's changes

commit-message-format is a cursor rule published in the GitHub repository holtwood/awesome-cursorrules-zh (231 stars, last pushed 27d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 186 tokens. 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.