fec-dependency-upgrade
Installation
SKILL.md
Dependency upgrade
Suitable for front-end dependency upgrades, bug fixes, major version migrations and lockfile risk reviews. Load references/dependency-upgrade-workflow.md when you need specific processes and checklists.
Purpose
Reduce disruptive changes, supply chain risks, and CI regressions by upgrading dependencies in a provenance-driven and small-batch verification manner.
Procedure
- Establish a baseline of truth: Read package manager, lockfile, Node version, workspace scope, CI commands, and current verification status.
- Classified upgrade goals: security fixes, patch upgrades, minor version upgrades, major version migrations, framework migrations, build tool migrations, or dependency cleanup.
- Verify sources: For version-sensitive libraries, read official release notes, migration guide, peer dependency, Node/browser support and deprecation items.
- Split into smaller batches: Security patches can be processed centrally; large versions, build tools, frameworks and testing tools must be verified in separate batches.
- Address compatibility boundaries: Check for ESM/CJS, TypeScript types, CSS handling, SSR/RSC, plugin APIs, peer dependencies, and polyfill changes.
- Run the verification matrix: at least cover install, typecheck, unit/component tests, and build; for key applications, add E2E, Storybook, or manual smoke.
- Synchronization documentation: Record upgrade reasons, versions, destructive changes, migration commands, rollback methods, and paths that still require manual verification.