migrate-claude

Migrates Claude project assets into Codex-facing repository configuration files.

3|Updated Jun 7, 2026
One-click install
npx skills add https://github.com/MLShukai/ResoniteIO --skill migrate-claude-mlshukai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-claude
Source: https://github.com/MLShukai/ResoniteIO/tree/main/.agents/skills/migrate-claude
Command: npx skills add https://github.com/MLShukai/ResoniteIO --skill migrate-claude-mlshukai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams moving from Claude Code to Codex need to port skills, agents, and guidance documents without losing information or blindly overwriting existing Codex-side content, and mechanical scripts alone cannot handle the judgment calls involved. ## Core Features & Use Cases - Settings synchronization check: Runs just migrate-codex --check to verify that .codex/rules/default.rules stays in sync with .claude/settings.json and .claude/settings.container.json. - Guided manual migration: Provides a step-by-step procedure for porting .claude/skills/, .claude/agents/*.md, and CLAUDE.md knowledge into .agents/skills/, .codex/agents/*.toml, and AGENTS.md. - Decision criteria: Defines rules for what belongs in the script versus manual judgment, such as never reverse-syncing Codex-only skills and never generating .codex/config.toml or personal environment settings. - Use Case: After updating a Claude skill, run this workflow to decide which parts should be reflected in the Codex-side skill, replacing Claude-specific terminology like CLAUDE.md or Claude-only permissions with Codex-meaningful equivalents. ## Quick Start Ask the assistant to migrate the Claude skills and agents in this repository to their Codex equivalents and verify the result with just migrate-codex --check.

Frequently Asked Questions about migrate-claude

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

FAQPage Schema
How do I migrate Claude skills to Codex agents?

Read both the source Claude skill and any existing Codex-side file, then manually port only the procedures Codex needs into .agents/skills/ or .codex/agents/*.toml. Run just migrate-codex --check first to confirm settings-derived rules are synchronized.

What does just migrate-codex automate versus handle manually?

The just migrate-codex command only regenerates .codex/rules/default.rules from .claude/settings.json and settings.container.json. Skills, agents, and prose guidance require manual judgment because simple path or name substitutions would change meaning.

Should Codex skills be synced back to the .claude directory?

No. Codex-specific skills live only in .agents/skills/ and are never reverse-synced to .claude/skills/. Neither side is treated as the single source of truth; the repository's current operational practice takes priority.

What Claude-specific content should not be migrated to Codex?

Do not migrate Claude-only permissions, references to CLAUDE.md or Claude Code, or personal environment settings. The workflow also never generates .codex/config.toml, auth state, or session data.

How do I verify a Claude to Codex migration worked?

Run just migrate-codex --check to confirm rules are in sync, then run pre-commit on scripts/migrate_codex.py, .codex/rules/default.rules, and the changed skill files to validate the migration output.