dependency-upgrades

Upgrade npm dependencies incrementally with validation gates and engineer approval.

4|Updated Apr 20, 2018
One-click install
npx skills add https://github.com/entorenee/dotfiles --skill dependency-upgrades-entorenee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-upgrades
Source: https://github.com/entorenee/dotfiles/tree/main/nix/module/claude/config/skills/dependency-upgrades
Command: npx skills add https://github.com/entorenee/dotfiles --skill dependency-upgrades-entorenee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a systematic, phased approach to upgrading npm dependencies across one or more packages while minimizing breakage and ensuring each major version bump is validated before proceeding. It prevents sweeping, error-prone updates by enforcing single-major-step progress, clear validation gates, and explicit engineer approval points.

Core Features & Use Cases

  • Phased upgrade workflow: Assess, baseline, research, execute phased updates, validate, engineer gate, and record progress for multi-session upgrades.
  • Strict validation gates: Require zero TypeScript errors, zero ESLint errors, all tests passing, and a successful production build (engineer-run) before advancing.
  • Peer dependency resolution and coupled-updates guidance: Recommendations for packages that must be updated together, override usage as a last resort, and migration research protocol.
  • Multi-session memory and communication: Templates and a memory file format to track progress across sessions and structured reporting for handoffs.

Quick Start

Run a phased upgrade by assessing npm outdated, pinning a clean baseline, updating the smallest safe set of major versions, running AI-led tsc/lint/tests, and requesting the engineer to run the production build before proceeding.

Frequently Asked Questions about dependency-upgrades

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely upgrade npm major dependencies across multiple packages?

Safely upgrading npm major dependencies requires a phased workflow: assess outdated packages, pin a clean baseline, update the smallest safe major version set, and validate tsc, lint, and tests before proceeding. This prevents sweeping breakage in multi-package repositories.

How do I resolve peer dependency conflicts during an npm migration?

Resolving peer dependency conflicts during npm migration involves identifying coupled packages that must update together and researching migration protocols. Using npm overrides is recommended only as a last resort when coupled-update guidance cannot resolve the dependency tree.

What is the best way to track npm upgrade progress across multiple sessions?

Tracking npm upgrade progress across sessions uses persistent memory files and structured reporting templates. This multi-session memory format records completed phases, validation gate statuses, and engineer handoff notes to ensure seamless continuation of incremental major version bumps.

What validation gates are required before advancing an npm dependency upgrade?

Validation gates for npm dependency upgrades require zero TypeScript errors, zero ESLint errors, and all tests passing. An engineer-run production build is also mandatory before advancing, ensuring the phased update does not introduce hidden runtime failures.

Can I automate git commits during a phased npm dependency upgrade?

Automated git operations are prohibited during phased npm dependency upgrades without explicit engineer approval. The workflow enforces manual engineer gates for production builds and version control actions to maintain safety during incremental major version bumps.