AI Migrate (aimig)

AI Migrate is a VS Code extension and standalone CLI tool designed to streamline the management of AI coding rules. It allows you to easily convert rule definitions between various AI-assisted IDE and CLI formats, ensuring your coding standards are consistent across all your tools.

Supported Formats

Features

• Full Agentic Migrations: Seamlessly migrate all capabilities — rules, skills (including symlinks), MCP servers, and event lifecycle hooks — between formats.
• Multi-Format Support: Convert rules and capabilities between all 8 supported formats.
• Automatic Detection: Automatically detects rules, skills, MCPs, and event hooks in your workspace.
• One-Click Conversion: Convert rules directly from the "Detected Rules" side panel.
• Bulk Conversion: Convert entire folders or all rules for a given format at once.
• Rule Management: Delete obsolete or incorrect rules directly from the extension view.
• Live Updates: The view automatically refreshes when changes are made.
• Standalone CLI: Use from the terminal without VS Code — great for CI/CD pipelines.

VS Code Extension Usage

1. Open the Rules Converter View: Click on the ruler icon in the Activity Bar to open the "Rules Converter" side panel.
2. View Detected Rules & Capabilities: The extension will scan your workspace and list all detected rules, skills, MCP servers, and event hooks, grouped by format.
3. Migrate Workspace Capabilities:
   • Click the Migrate Workspace icon (🔄) in the panel toolbar.
   • Select the source format to migrate FROM.
   • Select the target format to migrate TO.
   • All rules, skills, MCP configs, and hooks will be migrated/merged.
4. Convert a Rule:
   • Hover over a rule in the list.
   • Click the "Convert Rule" icon (or right-click and select "Convert Rule").
   • Select the target format from the quick pick list.
5. Convert All Rules in a folder/format:
   • Hover over an IDE group or subfolder.
   • Click the "Convert All Rules" (⇄) icon.
6. Delete a Rule:
   • Hover over a rule in the list.
   • Click the trash icon to remove it.

Standalone CLI Usage

The CLI is available via npx without any installation:

# List all detected agent capabilities (rules, skills, MCPs, hooks) in the workspace
npx aimig scan

# Limit the scan to a single format
npx aimig scan --format cursor

# Migrate all capabilities (rules, skills, MCP, hooks) from Antigravity to the new agy format
npx aimig migrate --from antigravity --to agy

# Convert all Cursor rules to Claude Code format
npx aimig convert --from cursor --to claude-code

# Convert rules in a specific project
npx aimig convert --from antigravity --to gemini-cli --root ./my-project

# Preview migration without writing files
npx aimig migrate --from cursor --to agy --dry-run

# List installed plugins (Claude Code + Antigravity)
npx aimig scan-plugins

# Convert a plugin between Claude Code and Antigravity (writes to the target's global plugins dir)
npx aimig convert-plugin --plugin caveman --from claude-code --to antigravity
npx aimig convert-plugin --plugin caveman --from antigravity --to claude-code --out ./out

# List all supported formats
npx aimig list-formats

CLI Options

Plugin Conversion (Claude Code ⇄ Antigravity)

convert-plugin --from <fmt> --to <fmt> converts a whole plugin bundle between the two ecosystems. It is intentionally restricted to claude-code and antigravity.

The conversion relocates the manifest, splits/merges hooks, renames the MCP config, and copies skills/, agents/, rules/ (and any hooks/ / scripts/ support dirs) verbatim. By default the result is written to the target's global plugins dir; pass --out <dir> to write elsewhere, or --dry-run to preview. Hook commands that reference ${CLAUDE_PLUGIN_ROOT} are preserved with a portability warning.

Antigravity path conventions

Workspace skills live in .agents/skills/ and MCP in .agents/mcp_config.json (note the plural .agents). The singular .agent/skills, .agent/mcp_config.json, and .agent/hooks.json are still scanned but reported as deprecated. Global Antigravity config lives under ~/.gemini/antigravity-cli/ (skills/, mcp_config.json, plugins/).

Flat-File Format Notes (Claude Code & Gemini CLI)

Claude Code and Gemini CLI use a single flat Markdown file (CLAUDE.md / GEMINI.md) rather than one file per rule. The converter handles this automatically:

• Scanning: Splits the file by ## Heading sections — each becomes a separate rule in the tree view.
• Converting TO Claude Code/Gemini CLI: Rules are written as ## {rule name} sections, concatenated into the flat file.
• Converting multiple rules: The file is freshly written for the first rule, then subsequent rules are appended.

Known Issues

• Ensure your rule files are valid Markdown before converting.
• For Claude Code/Gemini CLI formats, very long rules may exceed token limits recommended by those tools (~500 tokens per file).

Release Notes

Enjoy using AI Migrate (aimig)!