ember-dossier / rules
Cursor rule0 starsChanged 47 days agoMITView on GitHub
Commit message standards — applied when creating git commits
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,157 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .forgetrail/AGENTS.mdAGENTS.md
- .forgetrail/CLAUDE.mdCLAUDE.md
- .cursor/rules/forgetrail-lessons-gate.mdcCursor rule
- .cursor/rules/forgetrail-lessons-mcp.mdcCursor rule
- .cursor/rules/forgetrail-phase-status.mdcCursor rule
- .cursor/rules/git-user-commits.mdcCursor rule
- .cursor/rules/npm-publish.mdcCursor rule
- .cursor/rules/smellcheck.mdcCursor rule
- ember-dossierSkill
- ember-dossierSkill
The file
We split this commit-messages.mdc into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Distinctive: line 8
Use these whenever you create a commit.
- Distinctive: line 16
Prefer a multi-line message.
- Distinctive: line 19
Blank line: after the subject.
- Very specific: line 24
ForgeTrail policy: Use plain -m or git commit -F path/to/msg.txt.
≈ “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.
Files
--- description: Commit message standards — applied when creating git commits alwaysApply: true --- # Commit Messages Use these whenever you **create a commit**. This file defines *how* to write the message. ## Ground truth - Base the commit message on **what is actually staged** (`git diff --staged`). Do not add, assume, or hallucinate features, files, or reasons not visible in that diff. ## Format (default for substantive commits) Prefer a **multi-line** message. 1. **Subject line (first line):** A short imperative summary (≈50–72 characters). 2. **Blank line** after the subject. 3. **Body:** Scope, what changed, and a short why when it is not obvious. **Trivial commits** may use a subject-only message. **ForgeTrail policy:** Use plain `-m` or `git commit -F path/to/msg.txt`. ## Tone - Clear, professional US English (complete sentences in the body).
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
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.