migrate-geminilisted

# Migrate Gemini workflows Move proven Gemini CLI workflows into this workspace without bulk-copying private history or silently changing behavior. Consumer Gemini CLI requests transitioned to Antigravity CLI in June 2026; continuing enterprise/API-key Gemini CLI remains a distinct path. Treat Gemini files as migration sources. Do not claim that Antigravity shares Gemini skill discovery, hook, permission, or lifecycle behavior unless the installed target has been separately validated. ## Safety rules - Start with inventory and a dry run. Do not mutate source Gemini files. - Never print or persist token values, environment values, credentials, or full chat transcripts. - Work on a branch or worktree and show the proposed file map before writing. - Require explicit user approval before running a non-dry-run import or replacing an existing file. - Treat hooks and MCP configuration as executable/security-sensitive configuration. Rebuild and review them; do not blindly copy them. ## Procedure ### 1. Define the scope Ask for the Gemini project or configuration directory and the 1–3 workflows that matter most. Prefer a narrow migration over an account-wide import. Inventory only the presence, path, and type of: - `GEMINI.md` files and imports - `.gemini/commands/` - `.gemini/skills/` and `.agents/skills/` - hook event names and command names (not secret environment values) - MCP server names and transport types (not credentials) - extensions and headless scripts that need m