Rulesync
One unified ruleset, every AI coding tool: automatically generate per-tool configs from a single source of truth.
Evidence shows the tool reads/writes config only within the project (.rulesync/, per-tool dirs); plugin targets are explicitly excluded from --targets "*", showing least-privilege awareness (2). The `prepare` script runs `pnpm generate` at install time, writing files without documented confirmation (1, deducted). Data flow (import/generate/convert paths) is clearly described (2); secretlint runs in CI (2); dependencies are exact-pinned, but no lockfile/audit evidence shown (2). The curl|bash single-binary install executes a remote script with no checksum or signature in the README (1, deducted). No rollback/undo of generated files is documented (1, deducted). Author identity is consistent across LICENSE and package. (2).
The README/package. tool-feature tables are script-generated and diff-verified (check:supported-tools), giving good self-consistency (2); exact-pinned dependencies and explicit engines (2); however, no concrete evidence of error messages or failure handling appears in the provided files, hence 1.
Audience and scenario (unifying rules across many AI coding tools) are very clearly defined (3); capability boundaries are delimited by the support matrix and deprecation notes (2); triggers are explicit CLI commands with distinct init/import/generate/convert responsibilities (2); three install channels with platform-specific notes (2).
README is well structured; support tables are auto-generated and checked against docs (3); install notes cover three channels including a brew-tap pitfall (3); naming is stable with deprecated aliases keeping behavior (3); Quick Start exists but no in-repo example files were provided (2); deprecation and known-limitation notes (ignore deprecation, Roo EOL, Kiro split) are exceptionally thorough (3); full MIT LICENSE (3); version mismatch between package (16.x) and the unfilled SECURITY.md template (5.1.x/4.0.x), and no CHANGELOG in evidence (2, deducted); maintenance signals (funding badge, automation) but no explicit maintenance commitment (2).
Outputs are standard per-tool config files with protections like excluding plugin dirs from wildcards (2); marginal value is clear: eliminates duplicate rule maintenance across tools (3); cost/benefit is reasonable overall, though the auto-generating prepare hook and remote-script install add integration cost (2).
Support matrices are script-generated and diff-verifiable, making claims traceable (2); badges corroborate with npm/GitHub metadata, but static review cannot execute verification (2); facts and inference are largely separated, with explicit ⚠️ deprecation markers (2).
- The recommended `curl -fsSL ... | bash` install executes a remote script with no checksum or signature; prefer npm/Homebrew or audit install.sh first.
- SECURITY.md is an unfilled GitHub template whose supported-version table (5.1.x/4.0.x) contradicts the actual 16.x versioning; the actual vulnerability reporting channel is unverifiable.
- The `prepare` hook auto-runs a generate command and writes files during dependency install; be aware before adopting.
- No CHANGELOG or lockfile appears in the evidence; audit the supply chain yourself.
- Publisher identity is unverified (unknown, not suspicious); apply normal open-source due diligence.
What does this agent do, and when should you use it?
Rulesync is a Node.js CLI that automatically generates configuration files for a wide range of AI development tools from unified AI rule files stored under a .rulesync/ directory. It supports selective generation across rules, ignore files, MCP, commands, subagents, skills, hooks, and permissions, and offers comprehensive import/export capabilities. Supported tools include Claude Code, Cursor, GitHub Copilot, Codex CLI, Cline, Kilo Code, OpenCode, Kiro, JetBrains Junie, and dozens more, alongside open standards like AGENTS.md and AgentsSkills. Beyond generation, the convert command transforms configurations directly between tools without writing .rulesync/ files. The project is MIT-licensed and distributed via npm, a Homebrew tap, and a single-binary install script.
rulesync init scaffolds the required directories, sample rule files, and a configuration file; rulesync fetch dyoshikawa/rulesync installs official skills; rulesync generate --targets "*" --features "*" batch-generates per-tool configs (rules, MCP, commands, subagents, skills, hooks, permissions) from the .rulesync/ source. For existing setups, rulesync import --targets claudecode/cursor/copilot pulls in CLAUDE.md, .cursorrules, or .github/copilot-instructions.md into .rulesync/**/*. rulesync convert --from cursor --to copilot,claudecode converts between tools in one shot without writing .rulesync/ files.
- A team using both Cursor and Claude Code wants a single ruleset without hand-syncing multiple config files.
- A developer migrating from Cursor to GitHub Copilot uses the convert command to turn .cursorrules into Copilot config directly.
- An existing repo has scattered configs (CLAUDE.md, copilot-instructions.md) that the import command consolidates into a unified .rulesync/ source.
- A platform engineer needs to configure MCP servers, commands, and skills consistently across many AI tools.
- An open-source maintainer wants AGENTS.md as the canonical source while generating vendor-specific configs for proprietary tools.
What are this agent's strengths and limitations?
- Supports dozens of AI coding tools (Cursor, Claude Code, Copilot, Codex CLI, Cline, Kiro, and more) with a per-feature support matrix covering rules, ignore, MCP, commands, subagents, skills, hooks, and permissions.
- Supports both project-scope and global-scope generation, plus open standards like AGENTS.md and AgentsSkills.
- Bidirectional capability: import consolidates existing configs, and convert translates between tools without adopting the .rulesync/ workflow.
- Well-covered distribution: npm, Homebrew tap, and single-binary installer, backed by a dedicated documentation site.
- The npm path requires a Node.js runtime; the Homebrew tap requires the two-argument tap form — the shorthand brew install dyoshikawa/rulesync/rulesync does not work.
- The ignore feature is deprecated in favor of permissions; existing configs are safe through 14.x but removal may come in a future major release.
- Several targets carry deprecation caveats: Roo Code is end of life (target zoocode instead), Kiro is split into kiro-cli and kiro-ide, and the legacy kiro target is a deprecated alias.
- Plugin packaging targets (claudecode-plugin, antigravity-plugin) are excluded from --targets "*" and require explicit --output-roots/--output-root selection.
How do you install or deploy this agent?
Install globally via npm: npm install -g rulesync. Or on macOS/Linux via the Homebrew tap (the tap lives inside the repo with no homebrew- prefix, so the two-argument form is required): brew tap dyoshikawa/rulesync https://github.com/dyoshikawa/rulesync && brew install rulesync. A single-binary option is also available: curl -fsSL https://github.com/dyoshikawa/rulesync/releases/latest/download/install.sh | bash.
How do you use this agent?
First run: rulesync init to create directories, sample rules, and config; optionally rulesync fetch dyoshikawa/rulesync to install official skills; then rulesync generate --targets "*" --features "*" to produce all configurations. With existing configs: rulesync import --targets claudecode (from CLAUDE.md), --targets cursor (from .cursorrules), or --targets copilot (from .github/copilot-instructions.md). Direct tool-to-tool conversion: rulesync convert --from cursor --to copilot,claudecode.