What problem does it solve? Migrating from Yarn Classic 1.x to pnpm often silently changes transitive dependency versions, and tools like pnpm import or passing tests cannot prove version equality. This Skill performs the migration and then mechanically compares yarn.lock, pnpm-lock.yaml, package-manager list output, and node_modules to expose every version drift down to grandchild packages. ## Core Features & Use Cases - Guided Migration Workflow: Converts Yarn resolutions to pnpm overrides, pins packageManager metadata, updates .npmrc, rewrites CI/Docker commands, and generates pnpm-lock.yaml from yarn.lock. - Mechanical Drift Audit: A bundled zero-dependency Python script compares lockfiles, installed node_modules, and yarn list/pnpm list JSON output, classifying drift as VERSION_SET_CHANGED, MAJOR_COLLAPSED, or MISSING_NAME with npm alias resolution. - Risk Triage & Reporting: Prioritizes production-path major collapses and missing packages, and produces a PR-ready report template with reproduction commands. - Use Case: You are reviewing a PR that migrates a monorepo with server/, global-app/, and global-app/server/ lockfile units from Yarn to pnpm. Run the all-locks and all-node-modules verifier modes to get a summary table proving exactly which transitive versions changed before approving. ## Quick Start Ask the agent to migrate my Yarn Classic project to pnpm and run the drift audit to verify every transitive dependency version matches.
