CURSOR EXTENSION

Share Cursor rules the way you share code.

RuleSync keeps .cursor rules, hooks, skills, and MCP config in a GitHub repository. Incoming updates are reviewed before they touch the workspace. Local edits become a proposal branch — never a write to main.

Get the extension View the repository

IncomingRemote changed. Diff it, then apply.

LocalYou changed it. Publish a proposal branch.

ConflictBoth sides moved. Resolve before sync.

RULESYNC acme-app acme/cursor-rules

↻

5 files need review.

PROJECT STATUS

Rules need your attention

Review the changes before they affect the project.

Review changes →

11Managed files

2Incoming

3Local changes

0Conflicts

↗

Proposal branch ready rulesync/stefan/20260831-1412

Create PR

Next best action Review remote updates

Overview

RULESYNC acme-app acme/cursor-rules

↻

5 files need review.

MANAGED CONTENT

Rules library

＋ New

Search rules and configuration

Rules3

✦Always use project conventions.cursor/rules/conventions.mdcSynced

✦Prefer TypeScript strict mode.cursor/rules/typescript.mdcIncoming

✦Write tests with the change.cursor/rules/testing.mdcLocal

Hooks1

⌁Review secrets before apply.cursor/hooks/pre-apply.jsonIncoming

Skills1

◇Scaffold a React component.cursor/skills/react-component/SKILL.mdLocal

Rules library

RULESYNC acme-app acme/cursor-rules

↻

5 files need review.

REVIEW QUEUE

Review remote updates

Open a native diff for every file before applying or publishing changes.

Incoming from GitHub2

Prefer TypeScript strict mode.cursor/rules/typescript.mdc

Pull

Review secrets before apply.cursor/hooks/pre-apply.json

Pull

Apply 2 remote changes

Changes

WHY

Team rules, versioned and reviewable.

Platform teams already keep coding standards in git. RuleSync does the same for AI-editor guidance — without dumping gitignored .cursor files onto main.

Three-way sync

Every file is compared against the last accepted baseline, your workspace, and GitHub. You see incoming, local, and conflict — not a silent overwrite.

Native diffs

Review happens in Cursor’s own diff tabs. Apply one file or all incoming updates after you have looked at them.

Proposal branches

Local edits publish to rulesync/… and open GitHub Compare. Main stays untouched. You create the pull request.

Risk prompts

Hooks, MCP, secrets-looking content, binaries, and large files ask for confirmation before apply or publish.

SETUP

Four steps, then the library.

Activate the workspace

Open the RuleSync icon in the Activity Bar and turn the extension on for this folder.

Connect GitHub

Pick the rules repo

Choose owner/repo and branch. Private repositories work. One source per workspace in this release.

Merge the generated manifest

RuleSync writes rulesync.yml for you and opens a pull request. Merge it once. You do not edit or maintain that file.

MANIFEST

Generated for you. Not something you maintain.

If the rules repo has no rulesync.yml, RuleSync creates the Cursor starter, publishes it on a proposal branch, and opens the pull request. After you merge that PR, RuleSync reads the file on its own. You keep working in .cursor — not in YAML.

version: 1

profiles:
  cursor-project:
    adapter: cursor
    scope: project
    source: .cursor
    mode: mirror

TRUST

Narrow access. Explicit writes.

Tokens live in Cursor secret storage — never in workspace settings or the repo.The GitHub App asks for Contents, Metadata, and Pull requests on the rules repository you install it on.

Main is not a write target.RuleSync re-checks the base SHA before publishing a proposal branch.

Untrusted workspaces stay read-only.Filesystem writes and publish require a trusted folder.