Use when a user asks to migrate or transfer AI-assistant context between two named supported IDEs or agent products. Handle selected skills, rules, prompts, commands, or MCP configuration with a scoped, verifiable plan.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Requires local Bash and filesystem read/write access for resolved migration targets. Python 3 is required for automatic MCP conversion and redaction. No network access.
permissions
["file_read","file_write","shell"]
description
Use when a user asks to migrate or transfer AI-assistant context between two named supported IDEs or agent products. Handle selected skills, rules, prompts, commands, or MCP configuration with a scoped, verifiable plan.
AI IDE Context Migration
Route
Resolve source, target, objects, scope, and workspace from the request and
environment. Ask only when a missing choice would change the destination.
The per-IDE reference describes product behavior; the script describes what is
automated. Flag a mismatch before applying.
Execution
Global scope defaults to skills. Project-backed objects require an explicit
workspace in the command.
Before copying a Skill, scan every source text file and reject literal
credentials or links outside that Skill; leave both source and target intact.
Existing rules and prompt targets follow --strategy: backup is the
default, skip preserves them, and overwrite replaces or merges them.
Keep whole config files and opaque project trees manual. Rebuild a
documented setting or migrate a dedicated supported object.
Never move secrets, OAuth/session state, runtime metadata, approval grants,
chat history, databases, or generated memory. Use manual reconstruction when
redaction or conversion is unclear.
Claude Desktop app MCP in Settings → Extensions and Settings → Connectors is UI-managed; do not infer or rewrite it from legacy JSON.
Use --dry-run to resolve the plan. If the user already requested the
migration and the target is unambiguous, apply the same command with
--yes --json in the same task; do not ask for redundant confirmation.
Report evidence and native target discovery.
Commands
Run bash scripts/smart-ide-migration.sh --help for flags. Commands run from
this Skill directory.
