ember-dossier / rules
Cursor rule0 starsChanged 47 days agoMITView on GitHub
Commit at end of every request when repo changed; descriptive messages; push still explicit
- Commits and pushes
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/commit-messages.mdcCursor rule
- .cursor/rules/forgetrail-lessons-gate.mdcCursor rule
- .cursor/rules/forgetrail-lessons-mcp.mdcCursor rule
- .cursor/rules/forgetrail-phase-status.mdcCursor rule
- .cursor/rules/npm-publish.mdcCursor rule
- .cursor/rules/smellcheck.mdcCursor rule
- ember-dossierSkill
- ember-dossierSkill
The file
We split this git-user-commits.mdc into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 18
If there is nothing to commit for that request, say so briefly and skip.
- Distinctive: line 19
If other unrelated local changes exist, stage only what this request touched.
- Distinctive: line 23
Do not: run git push, merge/rebase, or publish flows unless the user explicitly asks.
- Distinctive: line 27
If the user says not to commit, to leave changes uncommitted, or is mid-experiment, do not commit—summarize only.
≈ “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 at end of every request when repo changed; descriptive messages; push still explicit alwaysApply: true --- # Git commits and pushes ## Permission (read this first) **Running `git commit` is allowed and expected** whenever this rule applies. ForgeTrail **ship defaults** assume agents **do not** wait for the user to say “commit,” and **do not** leave completed request work unstaged by default. What stays restricted: **`git push`** (and merge/rebase/publish) still requires an **explicit** user request. If the user asks to **leave the tree dirty**, skip commits for that work. ## End of each request (default) When you **finish responding to a user request** and your work **changed tracked files** in this repo for that request, **before or as part of your wrap-up summary** you must **`git add`** the paths that belong to that request (only those paths) and **`git commit`** with a **good message** grounded in **`git diff --staged`** (see `.cursor/rules/commit-messages.mdc`). - If there is **nothing to commit** for that request, say so briefly and skip. - If other **unrelated** local changes exist, **stage only** what this request touched. ## Push and merge - **Do not** run `git push`, merge/rebase, or publish flows unless the user **explicitly** asks. ## When the user opts out If the user says **not** to commit, to **leave changes uncommitted**, or is mid-experiment, **do not** commit—summarize only.
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.