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.

The matrix bounds the per-tool research, so a full run also scouts outside it: Step 2.5 looks for coding agents rulesync does not target yet and proposes the strongest ones as new targets, so a tool gaining traction is not missed just because nobody has added it to the matrix by hand.

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, skills, hooks, permissions) and their scope markers, using the legend:
  • ✅ project mode, 🌏 global mode, 🎮 simulated (project only), 🔧 MCP tool config.

Do not hardcode the tool list from memory, re-read the matrix each run so the skill stays in sync with the README.