CRUX-Compress / rules
Cursor rule8 starsChanged 2 months agoMITView on GitHub
When committing changes, analyze commit messages and update .crux/crux.json version accordingly. Apply semantic versioning based on conventional commit prefixes:
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,183 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 repository35 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/crux-memories-integration.crux.mdcCursor rule
- .cursor/rules/crux-memories-integration.mdCursor rule
- .cursor/rules/_CRUX-RULE.mdcCursor rule
- .cursor/rules/docs-sync.crux.mdCursor rule
- .cursor/rules/docs-sync.crux.mdcCursor rule
- .cursor/rules/docs-sync.mdCursor rule
- .cursor/rules/example/coding-standards-demo.crux.mdcCursor rule
- .cursor/rules/example/coding-standards-demo.mdCursor rule
- .cursor/rules/ignore-example-rules.crux.mdCursor rule
- .cursor/rules/ignore-example-rules.crux.mdcCursor rule
- .cursor/rules/ignore-example-rules.mdCursor rule
- .cursor/rules/skill-and-agent-references.mdcCursor rule
- .cursor/rules/spec-agent-allocation.crux.mdCursor rule
- .cursor/rules/spec-agent-allocation.crux.mdcCursor rule
- .cursor/rules/spec-agent-allocation.mdCursor rule
- .cursor/rules/spec-implementation-hygiene.mdcCursor rule
- .cursor/rules/version-bump.crux.mdCursor rule
- .cursor/rules/version-bump.crux.mdcCursor rule
- .cursor/rules/zip-contents-protection.crux.mdCursor rule
- .cursor/rules/zip-contents-protection.crux.mdcCursor rule
- .cursor/rules/zip-contents-protection.mdCursor rule
- crux-skill-memory-compressSkill
- crux-skill-memory-crudSkill
- crux-skill-memory-extractSkill
- crux-skill-memory-indexSkill
- crux-skill-memory-meditation-coordinationSkill
- crux-skill-memory-meditation-ensembleSkill
- crux-skill-memory-meditation-quickSkill
- crux-skill-memory-meditation-reportSkill
- crux-skill-memory-meditation-researchSkill
- crux-skill-memory-meditation-reviewSkill
- crux-skill-memory-rebalanceSkill
- crux-skill-memory-reference-trackerSkill
- crux-utilsSkill
The file
We split this version-bump.md into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 7
When committing changes, analyze commit messages and update .crux/crux.json version accordingly.
- Very specific: line 22
Before creating a commit: - If the user asks you to commit changes, analyze the commit message type and bump .crux/crux.json version before …
- Distinctive: line 44
Only bump version once per commit, using the highest-impact change type
- Distinctive: line 46
Do not bump version for commits that don't follow conventional commit format (ask user to clarify)
≈ “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
Automatic Version Bumping Rule
When committing changes, analyze commit messages and update .crux/crux.json version accordingly.
Conventional Commit Version Rules
Apply semantic versioning based on conventional commit prefixes:
| Commit Type | Version Bump | Example |
fix: | Patch (0.0.X) | 1.0.0 → 1.0.1 |
docs:, style:, refactor:, perf:, test:, chore: | Patch (0.0.X) | 1.0.0 → 1.0.1 |
feat: | Minor (0.X.0) | 1.0.0 → 1.1.0 |
BREAKING CHANGE: in body or ! after type | Major (X.0.0) | 1.0.0 → 2.0.0 |
When to Apply
- Before creating a commit - If the user asks you to commit changes, analyze the commit message type and bump
.crux/crux.jsonversion before staging - Include .crux/crux.json in the commit - Stage the updated
.crux/crux.jsonalong with the other changes
Version Bump Logic
MAJOR.MINOR.PATCH
- MAJOR: Breaking changes (API incompatibility)
- MINOR: New features (backwards compatible)
- PATCH: Bug fixes and minor changes (backwards compatible)Examples
fix: correct typo in output message→ Bump patch: 1.2.3 → 1.2.4feat: add support for custom output directory→ Bump minor: 1.2.3 → 1.3.0feat!: change default compression format→ Bump major: 1.2.3 → 2.0.0refactor: simplify staging logic→ Bump patch: 1.2.3 → 1.2.4
Important
- Only bump version once per commit, using the highest-impact change type
- Reset lower version numbers when bumping higher ones (1.2.3 → 2.0.0, not 2.2.3)
- Do not bump version for commits that don't follow conventional commit format (ask user to clarify)
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.