commit-message-generation-rule

commit-message-generation-rule is a cursor rule for coding agents from holtwood/awesome-cursorrules-zh. It costs 0 tokens per session (360 once invoked), scanned A, original, MIT.

Rules for writing consistent Git commit messages, using labels such as feat for a feature, fix for a bug, and docs for documentation. A commit message records one set of code changes.

In plain words
What is it for?
Use them when recording new features, bug fixes, refactoring, tests, documentation, dependency changes, or breaking changes.
Why use it?
They make a project’s history easier to scan, search, and understand.

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-generation-rule
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 360 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.00360
Opus 5 $0.00000 $0.00180
Sonnet 5 $0.00000 $0.00072
Haiku 4.5 $0.00000 $0.00036

Measured 3d ago against content hash eca695d3153d, 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-generation-rule 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 3d 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/phoenix-docker-setup/commit-message-generation-rule.mdc · 32 lines

What it actually says

  • 始终建议使用一个带有可选小写范围的约定式提交信息。遵循以下结构: [可选范围]: [可选正文][可选页脚]

其中:

  • type: 以下之一:

    • build: 影响构建系统或外部依赖的更改 (例如, Maven, npm)
    • chore: 不修改 src 或测试文件的其他更改
    • ci: 对我们的 CI 配置文件和脚本的更改 (例如, Circle, BrowserStack, SauceLabs)
    • docs: 仅文档更改
    • feat: 一个新功能
    • fix: 一个 bug 修复
    • perf: 提高性能的代码更改
    • refactor: 既不修复 bug 也不添加功能地代码重构
    • style: 不影响代码含义的更改 (空格, 格式化, 缺少分号等)
    • test: 添加缺失的测试或更正现有测试
  • scope (可选): 描述代码库某个部分的名词 (例如, fluxcd, deployment)。

  • description: 对更改的简要总结,使用现在时。

  • body (可选): 对更改的更详细解释。

  • footer (可选): 一个或多个以下格式的页脚:

    • BREAKING CHANGE: (用于重大更改)
    • <issue_tracker_id>: (例如, Jira-123: 修复了认证中的 bug)
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. 3d ago First seen · 32 lines · 0 tokens per session scan A eca695d3153d

Subscribe to this mod's changes

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