Migrate
Skill huzaifa525/claude-code-optimizer/templates/.claude/skills/migrate
Optimize Claude Code token usage — 22 skills, 8 hooks, 6 rules. One npm install. Zero manual steps. Cut costs by 67%.
npx -y skills add huzaifa525/claude-code-optimizer --skill migrateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when the user wants to migrate, upgrade, or move from one framework, library, or API version to another.
SKILL.md
1.6 KB, as published. Nobody here has run it
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]