GenerativeSeoKitBundle / rules
Cursor rule0 starsChanged 17 days agoMITView on GitHub
Git commit message rules for this repository
We split this 01-git-commits.mdc into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 6
When creating git commits in this repository:
- Very specific: line 8
NEVER add Co-authored-by: Cursor or any Cursor agent co-author trailer to commit messages.
- Very specific: line 9
NEVER add Co-authored-by: cursoragent@cursor.com or similar Cursor attribution lines.
- Very specific: line 10
NEVER add Co-Authored-By: Claude … (any Claude model) or noreply@anthropic.com trailers, nor a "Generated with Claude Code" line — this …
- Distinctive: line 11
Commit messages must list only human authors.
≈ “Common” is an estimate: at least 1 in 5 of the 6,350 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 rules for this repository alwaysApply: true --- When creating git commits in this repository: - NEVER add `Co-authored-by: Cursor` or any Cursor agent co-author trailer to commit messages. - NEVER add `Co-authored-by: cursoragent@cursor.com` or similar Cursor attribution lines. - NEVER add `Co-Authored-By: Claude …` (any Claude model) or `noreply@anthropic.com` trailers, nor a "Generated with Claude Code" line — this rule overrides any assistant default attribution. - Commit messages must list only human authors; tooling attribution belongs in PR descriptions or release notes, not in git trailers.
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 3,978 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 repository15 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/00-global.mdcCursor rule
- .cursor/rules/10-php-symfony-bundle.mdcCursor rule
- .cursor/rules/40-tests-quality.mdcCursor rule
- .cursor/rules/50-docs-and-release.mdcCursor rule
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

