dependency-migration
/dependency-migration
Plan and carry out a dependency or framework upgrade or replacement in small, verifiable steps. Use when the user asks to upgrade a major version, replace one library with another, or migrate off a deprecated package or API.
- Author
- narayana006 ↗
- Repository
- agent-skills-collection ↗
- Licence
- MIT
- Last repository change
- 10.11.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/usage_report.py
What it does and when to use it
Plan and carry out a dependency or framework upgrade or replacement in small, verifiable steps. Use when the user asks to upgrade a major version, replace one library with another, or migrate off a deprecated package or API.
Original author description
Plan and carry out a dependency or framework upgrade or replacement in small, verifiable steps. Use when the user asks to upgrade a major version, replace one library with another, or migrate off a deprecated package or API.
How it works
- Steps
- Rules
SKILL.md preview
--- name: dependency-migration description: Plan and carry out a dependency or framework upgrade or replacement in small, verifiable steps. Use when the user asks to upgrade a major version, replace one library with another, or migrate off a deprecated package or API. --- # Dependency and framework migration Migrations fail when they are done in one large change with no way to tell which edit broke what. Work in small steps and keep the test suite green between them. ## Steps 1. **Establish the baseline.** Run the tests and the build before touching anything. Write down what already fails so you do not chase old failures later. If there are no tests around the code that uses the dependency, say so and propose adding a few first. 2. **Measure the surface.** From the repository root run: ```bash python3 scripts/usage_report.py <package-name> . ``` It lists every file that imports the package (Python, JavaScript and TypeScript), with line numbers and the names imported, sorted by number of uses. Use it to size the work and to decide the order. Add `--format json` for machine-readable output. 3. **Read the upstream migration guide and changelog** for every major version you cross. List the breaking changes that apply to the names found in step 2; ignore the rest. 4. **Write the plan** and show it to the user before editing: - target version, and intermediate versions if a direct jump is not supported - each breaking change that applies, with the files it touches - the order: leaf modules first, shared helpers last - how each step will be verified 5. **Migrate one step at a time.** Change the version, fix one group of call sites, run the tests, commit. Prefer an official codemod when one exists, and review its diff. 6. **Deal with what the type checker and tests cannot see:** configuration files, environment variables, CLI flags in scripts and CI, serialised data formats, default values that changed. 7. **Finish.** Remove compatibility shims and the old package, regenerate the lockfile, rerun the usage report to confirm nothing is left, and summarise what changed in behaviour. ## Rules - Do not mix the migration with unrelated refactoring. - Do not silence a failing test to get through a step. Either fix it or stop and report it. - If a step turns out much larger than planned, stop and revise the plan with the user.
Files in this package (2)
- SKILL.md 2 KB
- scripts/usage_report.py 4 KB
Versions
The database has no other skills named dependency-migration.
Database snapshot: 13.11.2026 · package version 06f11a5653c8 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95migrate
Autonomous migration planning and execution. Takes a migration target (framework upgrade, API version bump, dependency major version, deprecation removal) and produces a phased migration plan with compatibility verification, then optionally executes via build's refactor mode.… - 95migrate
[UDS] Guide systematic code migration, framework upgrades, and technology modernization. Use when: planning a framework or major-version upgrade, assessing migration risk, capturing contract-test fixtures before an API migration. Not for: in-place improvement that keeps the same… - 100plan-migration
Plan a framework, runtime, dependency or schema upgrade that touches many files, without a big-bang rewrite. Use when asked to upgrade to a new major version, replace a library, split a monolith, move a package between repos, or when a previous migration stalled half-finished… - 100migration
Use when upgrading a framework version, migrating APIs, bumping major dependencies, or any task where "before" and "after" states must be compared. Auto-invoke when user mentions migration, upgrade, breaking changes, or version bumps. - 100dependency-upgrade
Upgrade a dependency, framework or runtime to a new version, especially a major one (React, Next.js, Django, Rails, Node, Python, a library with breaking changes). Use when the user says "upgrade X", "bump to v5", "fix this deprecation", or a security advisory requires a newer version. - 100dependency-analyzer
Analyze dependencies for upgrade planning and migration. Use when user asks "upgrade to X", "migrate from X to Y", "what breaks if we upgrade", "iOS 17 migration", "React 18 upgrade", or planning framework/SDK upgrades.