seri-agent / rules
Cursor rule0 starsChanged 2 months agoApache-2.0View on GitHub
Feature branches and PRs against dev, never a direct push to main or dev.
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,329 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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/code-quality.mdcCursor rule
- .cursor/rules/hooks.mdcCursor rule
- .cursor/rules/pstack.mdcCursor rule
- perf-reviewSkill
- verify-seriSkill
- perf-reviewSkill
- thermo-nuclear-code-quality-reviewSkill
The file
We split this git-workflow.mdc into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
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
- Very specific: line 9
Do not push to main or dev.
- Very specific: line 12
When the work is verified, push the branch and open a PR with --base dev.
- Distinctive: line 19
Do not merge the PR. Hand off after it is open.
- Very specific: line 25
Default in-session review is pstack /interrogate (and /no-comments before the PR).
≈ “Common” is an estimate: at least 1 in 5 of the 6,873 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: Feature branches and PRs against dev, never a direct push to main or dev. alwaysApply: true --- # Git workflow Trunk is `dev`. New work lands via a feature branch and a pull request against `dev`. Do not push to `main` or `dev`. Do not open a PR that targets `main`. `main` is the release line. When the work is verified, push the branch and open a PR with `--base dev`. Do not fast-forward local `dev` or `main` and push it. Feature and bugfix work is pstack (`/poteto-mode`), including Opening a PR. Gates still run. Default review is `/interrogate` + `/no-comments`, plus `/blast-radius` before the PR. Thermo-nuclear is on-demand. Do not merge the PR. Hand off after it is open. Branch names: a descriptive slug (e.g. `feat/<slug>`). ## PR review Default in-session review is pstack `/interrogate` (and `/no-comments` before the PR). `/code-review` is user-triggered. Thermo-nuclear is user-triggered.
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.

