opensync / rules
Cursor rule410 starsChanged 9 months agoMITView on GitHub
description: Critical Git Safety Protocol globs: alwaysApply: true 🚨 NEVER USE git checkout TO REVERT CHANGES 🚨 MANDATORY GIT SAFETY RULES: Why this matters: Using git checkout blindly can destroy sophisticated implementations, complex prompts, provider-specific logic, and other valuable work that took significant time to develop. NEVER run these commands without explicit user approval: ALWAYS before any git operation: If user asks to "revert" something: This rule exists because careless git operations destroyed 2 days of work.
- Deletes or force-pushes
1 other project uses a version of this.
Adopted by
Most recently taken up by
- waynesutton/markdown-siteword for word, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- waynesutton/markdown-site★ 628100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
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 repository12 other files it gives its agents.
- .cursor/rules/about.mdcCursor rule
- .cursor/rules/changelog.mdcCursor rule
- .cursor/rules/convex2.mdcCursor rule
- .cursor/rules/convex-write-conflicts.mdcCursor rule
- .cursor/rules/dev2.mdcCursor rule
- .cursor/rules/help.mdcCursor rule
- .cursor/rules/opensync-ecosystem.mdcCursor rule
- .cursor/rules/rulesforconvex.mdcCursor rule
- .cursor/rules/sec-check.mdcCursor rule
- .cursor/rules/task.mdcCursor rule
- .cursor/rules/write.mdcCursor rule
- public/llms.txtllms.txt
The file
We split this gitruels.mdc into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
When user asks to "undo" changes: Read the current file, identify problematic sections, and manually edit to fix them
- Distinctive: line 41
Run git status first to check for uncommitted changes
- Distinctive: line 42
If there are uncommitted changes, STOP and ASK the user before proceeding
≈ “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: globs: alwaysApply: true --- --- description: Critical Git Safety Protocol globs: alwaysApply: true --- ## Critical Git Safety Protocol **🚨 NEVER USE `git checkout` TO REVERT CHANGES 🚨** **MANDATORY GIT SAFETY RULES:** - **NEVER run `git checkout -- <file>`** without first examining what you're about to destroy - **ALWAYS use `git diff <file>`** to see exactly what changes will be lost - **MANUALLY undo changes** by editing files to revert specific problematic sections - **Preserve valuable work** — if user says changes are bad, ask which specific parts to revert - **`git checkout` destroys ALL changes** — this can eliminate hours of valuable progress - **When user asks to "undo" changes**: Read the current file, identify problematic sections, and manually edit to fix them **Why this matters**: Using `git checkout` blindly can destroy sophisticated implementations, complex prompts, provider-specific logic, and other valuable work that took significant time to develop. ## Git Safety Rules - CRITICAL **NEVER run these commands without explicit user approval:** - `git reset --hard` - Destroys uncommitted changes permanently - `git checkout -- .` - Discards all working directory changes - `git clean -fd` - Deletes untracked files permanently - `git stash drop` - Deletes stashed changes **ALWAYS before any git operation:** 1. Run `git status` first to check for uncommitted changes 2. If there are uncommitted changes, STOP and ASK the user before proceeding 3. Suggest `git stash` to preserve changes if needed **If user asks to "revert" something:** 1. First clarify: revert committed changes or uncommitted changes? 2. Show what will be affected before doing anything 3. Get explicit confirmation for destructive operations This rule exists because careless git operations destroyed 2 days of work.
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.