rulesync-feature-research
Maps rulesync feature implementations to upstream coding-agent documentation. Use when evaluating rulesync issues, comparing any coding-agent client with rulesync source capability surfaces, checking support, or planning a client map.
Profile →npx skills add dyoshikawa/rulesync --skill rulesync-feature-research --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Rulesync Feature Research ## What Build a reproducible map between a coding-agent client, an upstream feature surface, and the local rulesync implementation. | Request target | Read | | ------------------------- | --------------------------------------------------------------------- | | `antigravity` | `references/antigravity.md` | | `augmentcode` | `references/augmentcode.md` | | `claudecode` |
What does the rulesync-feature-research skill do?
Maps rulesync feature implementations to upstream coding-agent documentation. Use when evaluating rulesync issues, comparing any coding-agent client with rulesync source capability surfaces, checking support, or planning a client map.
How do I install it?
Run `npx skills add dyoshikawa/rulesync --skill rulesync-feature-research --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From dyoshikawa/rulesync, a repository with 1,285 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.