Claude-code-optimizer migrate
Use when the user wants to migrate, upgrade, or move from one framework, library, or API version to another.
install
source · Clone the upstream repo
git clone https://github.com/huzaifa525/claude-code-optimizer
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/huzaifa525/claude-code-optimizer "$T" && mkdir -p ~/.claude/skills && cp -r "$T/templates/.claude/skills/migrate" ~/.claude/skills/huzaifa525-claude-code-optimizer-migrate && rm -rf "$T"
manifest:
templates/.claude/skills/migrate/SKILL.mdsource content
Migrate from $ARGUMENTS.
Steps
-
Understand the migration
- What is being migrated (framework, library, API version)?
- What are the breaking changes between versions?
- Are there official migration guides?
-
Audit current usage
- Grep for all imports/usages of the old library/API
- Count affected files
- Identify patterns used
-
Create migration plan
## Migration: [from] → [to] ### Affected Files ([count]) - [file] — [what needs to change] ### Breaking Changes - [old API] → [new API] ### Steps 1. Update dependencies 2. [migration steps] 3. Run tests -
Run tests BEFORE migration — establish baseline
[test command] -
Update dependencies first
npm install [new-package]@latest -
Apply migration file by file
- Replace old imports with new
- Update API calls to new syntax
- Handle renamed/removed functions
- Update types if needed
-
Run tests AFTER each file — catch issues early
-
Run full test suite at the end
-
Report:
## Migration Complete ### Summary - [X] files migrated - [Y] API calls updated - All tests passing ### Manual Review Needed - [anything that couldn't be auto-migrated]