RuleSync

CURSOR EXTENSION

Keep team rules in sync. Keep humans in control.

RuleSync gives your team one dashboard for shared Cursor rules, hooks, skills, and automation. Review incoming updates in a diff, pull only what you approve, and send local improvements back through a PR or MR.

Get the extension View the repository
IncomingThe team source changed. Review before pulling.
LocalYou improved something. Send it back through review.
ConflictBoth sides changed. You choose what wins.

WHY

One source of truth for every developer.

Cursor configuration is often gitignored, so team guidance slowly turns into five slightly different copies. RuleSync keeps it versioned, reviewable, and easy to adopt—without putting anyone’s personal setup on main.

Your whole Cursor toolkit

Manage rules, hooks, skills, agents, commands, MCP, and related configuration from one clear library.

See exactly what changed

Incoming and local updates open in Cursor’s native diff viewer. Pull one file, apply everything reviewed, or resolve a conflict yourself.

PRs, not mystery pushes

Local edits go to a rulesync/… proposal branch. RuleSync opens GitHub or GitLab so your normal team review can finish the job.

Extra care for powerful files

Hooks, MCP, executables, binaries, and secret-looking content need an explicit per-file approval. If the contents change, approval is required again.

Built for private repositories

Connect GitHub, GitLab.com, or trusted self-hosted GitLab. Credentials stay in Cursor’s secret storage, not in your project.

Quietly keeps watch

Check for shared updates on startup, when the dashboard opens, or on a schedule. Because “did anyone update the rules?” gets old quickly.

SETUP

From zero to synced in four steps.

1

Activate the workspace

Open the RuleSync icon in the Activity Bar and activate it for the current project.

2

Connect GitHub or GitLab

Use the RuleSync GitHub App, or connect GitLab with an api token. Private repositories work too.

3

Pick the rules repo

Choose the repository and branch containing the team’s root .cursor/ folder. Each folder has one source.

4

Review the first sync

Open diffs, approve sensitive files, and pull the configuration you want. From then on, RuleSync tracks what changed on either side.

LAYOUT

Drop in .cursor. That’s it.

No manifest and no mapping puzzle. RuleSync syncs repository-root .cursor/** and ignores existing rulesync.yml files. The shared branch stays read-only.

.cursor/
  rules/
  hooks.json
  skills/
  mcp.json

SAFETY REVIEW

Sensitive changes stop here.

RuleSync flags powerful files.Hooks, MCP configuration, executables, binaries, and possible secrets are called out automatically.

Review the actual change.Open the file in Cursor’s diff viewer. It cannot be applied or published until you approve it.

If the file changes, the approval expires.The updated version must be reviewed again before it can move anywhere.

1.1.2

  • New Ready for Review
  • New repository link
  • BREAKING update-check onFocus default
  • New local-only content
  • Fixed folder settings write
  • New GitLab.com and self-hosted GitLab
  • New per-file high-risk approval
  • New proposal-branch review links
  • New independent folder sources
  • New restore from remote
  • New local disable
  • New GitHub disconnect
  • Fixed revert of deleted files
  • BREAKING rulesync.yml mappings
  • BREAKING custom GitHub client IDs
  • BREAKING empty-repo default-branch creation
  • BREAKING workspace-scoped sources