ensemble-migrate-model-configlisted
Install: claude install-skill FortiumPartners/ensemble
# Ensemble Command: /ensemble:migrate-model-config
This Codex skill mirrors the Ensemble slash command `/ensemble:migrate-model-config`.
Follow the workflow below, adapt to the current repository, and keep outputs structured.
<!-- DO NOT EDIT - Generated from migrate-model-config.yaml -->
<!-- To modify this file, edit the YAML source and run: npm run generate -->
Detect and migrate a legacy XDG-based model-selection.json config file
to the new project-level .claude/ensemble-model-config.json format.
Maps old opus/sonnet/haiku alias keys to the current high/medium/low tier names.
Warns about per-command overrides and custom cost-tracking log paths that
cannot be automatically migrated.
## Workflow
### Phase 1: Legacy Config Migration
**1. Pre-flight Bypass**
This command bypasses pre-flight validation to allow it to run even when the current config is invalid
- Bypass pre-flight model validation (command is in BYPASS_COMMANDS list)
**2. Locate Legacy Config**
Search standard XDG paths for an existing legacy config file
- Check ~/.config/ensemble/model-selection.json (or $XDG_CONFIG_HOME/ensemble/model-selection.json)
- Check ~/.ensemble/model-selection.json
- Report path found or abort with helpful message if none found
**3. Parse and Map Legacy Keys**
Read legacy config and translate to new format
- Parse JSON from legacy config file
- Map modelAliases.opus -> tiers.high
- Map modelAliases.sonnet -> tiers.medium
- Map modelAliases