commit-message-english

A rule requiring Git commit messages—the notes attached to saved code changes—to be written in English. It also specifies a conventional format and a maximum subject-line length.

In plain words
What is it for?
It guides the wording and format of commit subjects, message bodies, and footers.
Why use it?
It keeps commit history consistent and readable for teams that use English as their shared language.

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/peiiii/nextclaw/commit-message-english
Clone the repo
git clone --depth 1 https://github.com/Peiiii/nextclaw

Made for: Cursor.

Per session 128 This file is loaded in full into every session.
When invoked 128 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.00128 $0.00128
Opus 5 $0.00064 $0.00064
Sonnet 5 $0.00026 $0.00026
Haiku 4.5 $0.00013 $0.00013

Measured yesterday against content hash b8b44b096757, 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-english 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/commit-message-english.mdc · 23 lines

What it actually says

Commit Message Language

All git commit messages must be written in English.

  • Use conventional commit format: type(scope): subject
  • Keep subject line under 72 characters
  • Body and footer in English
# ✅ GOOD
git commit -m "fix(ncp): resolve stream encoder tool call ordering"
git commit -m "feat(api): add pagination support"

# ❌ BAD
git commit -m "修复 NCP 流式编码器问题"
git commit -m "新增分页功能"
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. yesterday First seen · 23 lines · 128 tokens per session scan A b8b44b096757

Subscribe to this mod's changes

commit-message-english is a cursor rule published in the GitHub repository Peiiii/nextclaw (253 stars, last pushed yesterday), licensed MIT. It adds 128 tokens to every session, about $0.0006 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.