4 findingsStatic scanned
Puts Claude in your terminal to understand your codebase, edit files and handle git workflows.
80.2M installs/moSEE LICENSE IN README.md
Rulesync
dyoshikawa · App
Rulesync is a Node.js command line that keeps one set of AI rule files as the source of truth and generates the files each AI development tool expects. It handles rules, commands, MCP settings, ignore files, subagents and skills, and supports a long list of coding assistants and editors. You can import the files you already have into the shared source, or convert one tool's setup directly into another's. It suits teams that use more than one AI coding tool.
Written by ooruby from the README of rulesync 29.0.0.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
It removes the need to maintain a separate copy of your instructions for every AI coding tool you use.
What you could do with it
- Import the rule file you already keep for one coding tool, then generate the matching files for the others.
- Convert one tool's rules straight into another tool's format without adopting a shared source folder.
- Generate subagent and skill files for each tool that supports them from the same source files.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Unified AI rules management CLI tool that generates configuration files for various AI development tools
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 29.0.0, the file with digest sha512-KmV/X6RFInZCUP3YZkB4NxyrzsdHRqN2wpVr/hWYbkSik4k4ZxiULAl09sy6rGdgm6/jn3oq7f7BpqpeaOlUSA==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Run it with:
npx -y rulesync@29.0.0Pinned to 29.0.0, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- rulesync
- Version read
- 29.0.0
- Resolved
- 2026-10-10
Built from source, attested
npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.
- Repository
- github.com/dyoshikawa/rulesync
- Commit
- 4efba24d515f
- Built by
- github.com/actions/runner/github-hosted
- Registry publish attestation
- signed by npm · 2026-10-10
- Checked
- 2026-10-10
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/rulesync)About this listing
- Kind
- App
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-10
Similar apps
All appsVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.