migrate-claude

Name: migrate-claude
Availability: InStock
Author: claretagrapelike32

Plans a reversible migration of Claude Code project guidance into Codex configuration files.

Updated Aug 2, 2026

Search Tags:#game development #rollback #claude code #codex #migration #configuration #agents.md

Ready to run

npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill migrate-claude-claretagrapelike32

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migrate-claude
Source: https://github.com/claretagrapelike32/codex-ai-game-studio/tree/main/plugins/ai-game-studio-automation/skills/migrate-claude
Command: npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill migrate-claude-claretagrapelike32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Moving a game project from Claude Code to Codex requires translating CLAUDE.md guidance, slash commands, agents, and hooks without losing the original setup or silently merging conflicting policies. ## Core Features & Use Cases - Project Inspection: Scans CLAUDE.md, .claude/, AGENTS.md, .codex/, engine markers, and uncommitted work without modifying anything. - Reversible Migration Plan: Generates a plan.json mapping Claude slash commands to namespaced $ai-game-studio skill references and agent definitions to .codex/agents/. - Safety Gates: Blocks unsupported Claude-only model names, tool declarations, memory fields, and fixed turn limits, then requires verbatim digest confirmation before applying changes. - Use Case: A studio adopting Codex runs the migration plan on an existing Claude Code game project, reviews every proposed destination, confirms the digest, applies the plan, and validates skills, platform, and tests with a rollback path. ## Quick Start Inspect this Claude Code game project and propose a reversible Codex migration plan with backups and rollback steps.

Frequently Asked Questions about migrate-claude

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I migrate a Claude Code project to Codex?▼

Run the migrate claude command with the project root and an output plan path, review every proposed destination, then confirm the digest verbatim and apply the plan with pack apply. Finish by validating skills, platform, and project tests.

What happens to Claude slash commands during migration?▼

Claude slash commands are converted into namespaced $ai-game-studio skill references in the migration plan. Engine and project guidance becomes root or scoped AGENTS.md, and supported agent definitions move under .codex/agents/.

Does the migration modify my original Claude files?▼

No, the original CLAUDE.md and .claude files are left unchanged for comparison and rollback. The plan includes backups and rollback operations, and a transaction ID is reported after applying.

What Claude features are blocked from migrating to Codex?▼

Claude-only model names, tool declarations, memory fields, fixed turn limits, and unsupported paths are blocked from entering Codex runtime files. They are flagged in the plan instead of being silently copied.

What happens if AGENTS.md already has my own guidance?▼

The migration stops at the proposal stage and shows the overlap when destinations contain user-authored guidance. It never silently merges policy text whose precedence is unclear.