deps-migrate_skill

This skill helps you migrate dependencies and APIs across projects by guiding library replacements and API pattern updates with a test-first workflow.
  • Shell

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill vdustr/vp-claude-code-marketplace --skill deps-migrate

  • SKILL.md11.2 KB

Overview

This skill automates and guides dependency or API-pattern migrations across a codebase. It identifies usage of a source library or deprecated API, verifies migration strategies with tests in a safe /tmp sandbox, and produces a validated, file-by-file migration plan before any destructive changes.

How this skill works

The skill scans the repository to detect package manager, monorepo layout, tests, and code usage of the source API. It builds an API mapping by consulting official docs, community migration guides, and code analysis, then verifies transformations on representative snippets in an isolated /tmp workspace. After validation it creates an execution plan, applies changes file-by-file, runs CI checks, and only removes the source dependency after full verification.

When to use it

  • Replace one library with another (e.g., moment.js → date-fns).
  • Migrate deprecated API patterns inside the same library (e.g., React forwardRef changes).
  • Plan a gradual upgrade using a compat layer or codemods.
  • Validate migration approach safely before bulk edits.
  • Prepare a compliance-aware plan (changesets, commits, CI).

Best practices

  • Detect codemods or compat layers first; prefer official tools where available.
  • Always run test-first verification in /tmp with representative samples before batch changes.
  • Build a complete API mapping table and document behavioral differences.
  • Respect repo conventions: changesets, conventional commits, CI hooks, and pre-commit checks.
  • Keep the source library installed until final verification passes to allow rollback.

Example use cases

  • Replace moment.js with date-fns and update format tokens across files.
  • Migrate from webpack to vite including config and plugin replacements.
  • Remove deprecated React forwardRef patterns and adapt components to the new API.
  • Swap lodash for a compat shim then incrementally convert calls to native APIs.
  • Port Vue Options API usages to Composition API with validated snippets.

FAQ

No. The source library stays installed until final verification passes to ensure safe rollback and avoid breaking installs.

What if no direct API equivalent exists?

I document the gap, propose a custom wrapper or manual steps, and ask for user direction before proceeding.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational