research-tool-updates
Research recent upstream releases of every rulesync target tool, detect capabilities rulesync has not yet followed, and file one GitHub issue per tool for the gaps.
Profile →npx skills add dyoshikawa/rulesync --skill research-tool-updates --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.
# Research Tool Updates TARGET = the user's request Purpose: for every target tool rulesync supports, investigate the tool's recent releases (official release notes / GitHub releases preferred), compare them against rulesync's current implementation, and open a per-tool GitHub issue for any upstream capability rulesync has not yet caught up with. When an issue for that tool already exists, supplement it with a comment instead of filing a duplicate. ## Step 0: Determine Scope - If `TARGET` is provided, investigate **only that tool**. Accept either the display name (e.g., `Claude Code`) or the `--targets` id (e.g., `claudecode`). Validate it against the supported tool list from Step 1; if it does not match any known tool, stop and report the valid options. - If `TARGET` is empty, investigate **all** supported target tools. ## Step 1: Enumerate Supported Target Tools Read the **`Supported Tools and Features`** matrix in `README.md`. This matrix is the authoritative source of what rulesync supports today. Extract, for each in-scope tool: - The display name and the `--targets` identifier. - The currently supported feature columns (`rules`, `ignore`, `mcp`, `commands`, `subagents`, `skil
- Step 0: Determine Scope
- Step 1: Enumerate Supported Target Tools
- Step 2: Launch One Research Subagent per Target Tool
- Step 3: Consolidate Findings per Tool
- Step 4: File One GitHub Issue per Tool with Gaps
- Step 4-1: Check for an Existing Issue (mandatory)
- Step 4-2: Supplement the Existing Issue with a Comment
- Step 4-3: Create a New Issue
- Step 5: Report
pnpm run dev generate --targets <id> --features "*" --dry-run pnpm run dev generate --targets <id> --features "*" --global --dry-run gh label list --limit 100 gh issue list --state all --search "<tool name>" --json number,title,url,state,labels gh issue list --state all --search "<--targets id>" --json number,title,url,state,labels gh issue view <issue_number> gh issue view <issue_number> --comments gh issue comment <issue_number> --body "<comment>" gh issue create --title "<title>" --body "<body>" --label "<label1>,<label2>"
What does the research-tool-updates skill do?
Research recent upstream releases of every rulesync target tool, detect capabilities rulesync has not yet followed, and file one GitHub issue per tool for the gaps.
How do I install it?
Run `npx skills add dyoshikawa/rulesync --skill research-tool-updates --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.