# Vp Deps Migrate

> Replace a library or migrate deprecated API patterns. Use when switching dependencies, frameworks, build tools, or APIs. Boundary: use vp-deps-upgrade for a version change within the same dependency.

- Skill: `vdustr/vp-deps-migrate` (Agent Skill, multi-file: 7 files)
- Install (CLI): `npx skillmds@latest add vdustr/vp-deps-migrate`
- Raw SKILL.md: https://api.skillmd.com/api/skills/vdustr/vp-deps-migrate/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: VdustR (https://skillmd.com/u/vdustr)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/vdustr/vp-deps-migrate

---


# Dependency Migration

Map behavior and ownership before changing imports. A successful migration
preserves required runtime behavior, lifecycle, data compatibility, and
operational expectations—not merely type-checking.

## Workflow

1. Identify repository constraints, package ownership, runtime targets, and
   relevant tests.
2. Classify usages by behavior and lifecycle instead of applying blind
   replacement.
3. Compare current official guidance, compatibility layers, and related package
   requirements.
4. Define success evidence and material risks before editing.
5. Migrate in reviewable slices, removing obsolete code introduced by the old
   dependency.
6. Verify focused behavior first, then broader integration and repository
   checks.

Read only the relevant reference:

- `references/migration-patterns.md`
- `references/package-managers.md`
- `references/repo-conventions.md`
- `references/context7-integration.md`
- `references/confidence-index.md`

## Related skills

- [`vp-deps-upgrade`](https://github.com/VdustR/skills/tree/main/skills/vp-deps-upgrade)
  when the work changes versions within the same dependency.
- [`vp-autodev`](https://github.com/VdustR/skills/tree/main/skills/vp-autodev)
  when the migration must continue through PR delivery and review.