agentinit / rules
Cursor rule1 starsChanged 12 days agoMITView on GitHub
Git commit message conventions for this repository
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,144 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 repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/agentinit-vitest.mdcCursor rule
- .cursor/rules/io-safety.mdcCursor rule
- .cursor/rules/pure-modules.mdcCursor rule
- .cursor/rules/registry-content.mdcCursor rule
- .cursor/rules/tests.mdcCursor rule
- commit-changesSkill
- implement-taskSkill
- new-featureSkill
- pr-summarySkill
- refactorSkill
- review-archSkill
- review-taskSkill
- write-fragmentSkill
- write-testsSkill
The file
We split this git-commits.mdc into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
ALWAYS use Conventional Commits: <type>(<optional scope>): <subject>
- Very specific: line 14
NEVER add Co-authored-by: trailers or any AI/tool attribution (e.g.
≈ “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: Git commit message conventions for this repository alwaysApply: true --- # Git Commits - ALWAYS use [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/): `<type>(<optional scope>): <subject>` - Types: `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `build`, `ci`, `chore`, `revert` - Scopes (optional): `cli`, `detect`, `registry`, `plan`, `targets`, `io`, `ui`, `docs`, `deps`, `ci`, `release` - Subject: imperative mood, lowercase, no trailing period, ≤ 72 characters - Breaking changes: add `!` after the type/scope and a `BREAKING CHANGE:` footer - Body is optional; use it to explain *why*, wrapped at 72 characters. - NEVER add `Co-authored-by:` trailers or any AI/tool attribution (e.g. "Generated with…", "Made with…") to commit messages. - One logical change per commit. ```text # ✅ Good feat(detect): resolve installed package versions from node_modules fix(targets): serialize cursor globs as comma-separated string # ❌ Bad Added detection stuff. feat: add detector Co-authored-by: Some Agent <agent@example.com> ```
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.