rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
Best use case
rulesync is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
Teams using rulesync should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/rulesync/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How rulesync Compares
| Feature / Agent | rulesync | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Rulesync Rulesync generates and synchronizes AI rule configuration files across 20+ coding tools (Claude Code, Cursor, Copilot, Windsurf, Cline, Gemini CLI, and more) from a single set of unified rule files in `.rulesync/`. ## Quick Start ```bash # Install npm install -g rulesync # New project: initialize config, rules, and directory structure rulesync init # Import existing AI tool configs into unified format rulesync import --targets claudecode # From CLAUDE.md rulesync import --targets cursor # From .cursorrules rulesync import --targets copilot # From .github/copilot-instructions.md # Generate tool-specific configs from unified rules rulesync generate --targets "*" --features "*" ``` ## Core Workflow 1. **Init** - `rulesync init` creates `rulesync.jsonc` config and `.rulesync/` directory with sample rules 2. **Write rules** - Add shared AI rules in `.rulesync/rules/`, MCP configs in `.rulesync/mcp/`, commands in `.rulesync/commands/` 3. **Generate** - `rulesync generate` produces tool-specific files (CLAUDE.md, .cursorrules, .github/copilot-instructions.md, etc.) 4. **Verify** - `rulesync generate --dry-run` previews changes; `--check` validates files are up to date (useful in CI) ## Key Commands | Command | Purpose | | ------------------------------------------------ | ------------------------------------------------ | | `rulesync init` | Scaffold project with config and sample rules | | `rulesync generate --targets "*" --features "*"` | Generate all tool configs from unified rules | | `rulesync import --targets <tool>` | Import existing tool config into unified format | | `rulesync fetch owner/repo --features skills` | Fetch rules or skills from a remote repository | | `rulesync install` | Install skill sources declared in rulesync.jsonc | | `rulesync generate --check` | CI check that generated files are up to date | | `rulesync generate --dry-run` | Preview changes without writing files | ## Detailed Reference - [Installation](./installation.md), [Quick Start](./quick-start.md) - [Why Rulesync?](./why-rulesync.md), [Configuration](./configuration.md), [Global Mode](./global-mode.md), [Simulated Features](./simulated-features.md), [Declarative Sources](./declarative-sources.md), [Official Skills](./official-skills.md), [Dry Run](./dry-run.md), [Case Studies](./case-studies.md) - [Supported Tools](./supported-tools.md), [CLI Commands](./cli-commands.md), [File Formats](./file-formats.md), [MCP Server](./mcp-server.md) - [Programmatic API](./programmatic-api.md) - [FAQ](./faq.md)
Related Skills
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
security-scan-diff
Scan for malicious code in git diff between a tag/commit and HEAD
release-dry-run
Dry run for release: summarize changes since last release and suggest version bump.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
git-worktree-runner
Manages git worktrees using git-worktree-runner (gtr). Use when the user needs to create, list, remove, or navigate worktrees with `git gtr` commands, open editors or AI tools in worktrees, manage parallel development branches, or check out GitHub PRs (including from forks) into worktrees.
draft-release
Draft a new release of the project.
create-scrap-issue
Create a GitHub issue that consolidates passed content into a single scrap issue with background context and solution details, labeled as maintainer-scrap. Use when the user wants to create a scrap issue, jot down notes as a GitHub issue, or save findings for later.
create-issue
Create a GitHub issue with detailed description, purpose, and appropriate labels
review-pr
Review a pull request for code quality and security issues. Use when the user wants to review a PR, check PR code changes, or audit a pull request. Triggers on: "review PR", "review pull request", "check this PR", "/review-pr".
review-and-comments
Review a PR for code quality and security issues, then post review comments on it. Runs review-pr followed by post-review-comments sequentially.
rebase-latest-main
Fetch latest origin/main and rebase it onto the current branch, resolving conflicts if necessary. Use when the user wants to rebase on main, update their branch with latest main, or sync with upstream.
post-review-comments
Post line-level review comments and an overall review comment on a PR in English with a natural, concise writing style