agentleFS
Sign inStart free
PeiiiiPeiiii/nextclaw/.cursor/rules/commit-message-english.mdc

nextclaw / rules

Cursor rule263 starsChanged 35 days agoMITView on GitHub

Use English for git commit messages

The file

We split this commit-message-english.mdc into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All git commit messages must be written in English.

    line 8
  2. Very specific:

    Use conventional commit format: type(scope): subject

    line 10
  3. Distinctive:

    Keep subject line under 72 characters

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
commit-message-english.mdc
---
description: Use English for git commit messages
alwaysApply: true
---

# 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

```bash
# ✅ 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 "新增分页功能"
```

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free