levistack / rules
Cursor rule0 starsChanged 18 days agoMITView on GitHub
Conventional Commits format, one purpose per commit, and never commit or push unless asked.
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 repository57 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/comments.mdcCursor rule
- .cursor/rules/git-workflow.mdcCursor rule
- .cursor/rules/manage-stack.mdcCursor rule
- .cursor/rules/no-worktrees.mdcCursor rule
- manage-stackSkill
- convert-as-skillSkill
- create-agentSkill
- create-agents-mdSkill
- create-commandSkill
- create-hookSkill
- create-ruleSkill
- create-skillSkill
- retrospectiveSkill
- super-architectureSkill
- super-cachingSkill
- super-elixirSkill
- super-nodejsSkill
- super-protobufSkill
- super-tech-blueprintSkill
- atomic-semantic-commitSkill
- code-reviewSkill
- create-bruno-collectionSkill
- create-documentationSkill
- create-ticketsSkill
- ready-specSkill
- write-adrSkill
- write-changelogSkill
- write-mr-descriptionSkill
- write-planSkill
- write-postmortemSkill
- write-runbookSkill
- noslopSkill
- output-saversSkill
- safe-refactorSkill
- tddSkill
- verifySkill
- get-movingSkill
- later-listSkill
- standupSkill
- challenge-meSkill
- codebase-learnerSkill
- researchSkill
- second-opinionSkill
- traceSkill
- color-kitSkill
- design-system-kitSkill
- diagramSkill
- infographicSkill
- product-polish-workflowSkill
- prototype-wireframeSkill
- ui-ux-kitSkill
- evidenceSkill
- find-skillsSkill
- handoffSkill
- rumblingSkill
- use-levistackSkill
The file
We split this commit-messages.mdc into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use Conventional Commits unless the repository defines a stricter convention:
- Very specific: line 24
Add a ticket reference when one exists (fix(auth): [PROJ-123] reject expired tokens).
- Distinctive: line 25
Add a body only when motivation or rollout context helps review.
- Distinctive: line 29
Never commit, push, create a branch or open a review unless the user or the active workflow asks for it.
≈ “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: "Conventional Commits format, one purpose per commit, and never commit or push unless asked." alwaysApply: true --- # Commit messages Use Conventional Commits unless the repository defines a stricter convention: `<type>(<optional-scope>): <optional-[TICKET]> <imperative description>` | Type | When | |---|---| | `feat` | New behavior or capability | | `fix` | Bug fix | | `refactor` | Restructure without behavior change | | `perf` | Performance improvement | | `test` | Add or correct tests | | `docs` | Docs, rules, skills | | `build` / `ci` | Dependencies, tooling, pipelines | | `chore` / `revert` | Housekeeping, reverts | - Subject: imperative, lowercase, 72 characters or fewer, no trailing period. - Add a ticket reference when one exists (`fix(auth): [PROJ-123] reject expired tokens`). - Add a body only when motivation or rollout context helps review. Explain why, not what. - Breaking change: add `!` after the type and a `BREAKING CHANGE:` footer. - One purpose per commit. If the diff has two purposes, make two commits. Never commit, push, create a branch or open a review unless the user or the active workflow asks for it. ## Incorrect ``` Added new script for bulk migration fix bug Updated dependencies ``` ## Correct ``` feat(scripts): add bulk migration script fix(runner): correct checkpoint index off-by-one on resume build(deps): bump tqdm to 4.70.0 ```
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.