What problem does it solve? This repository deliberately commits no lockfile, so every npm install (local, CI, Vercel) resolves the newest version matching each caret range independently. That means deploys can break with zero code changes, CI-green does not guarantee deploy-safe, and major bumps like ESLint 10 can crash the toolchain. This Skill makes that always-latest doctrine operational and safe. ## Core Features & Use Cases - Currency checks: Interprets npm outdated and npm ls --depth=0 output, distinguishing automatic minor/patch updates from majors needing deliberate bumps. - Major-bump runbook: A six-step procedure covering changelog review, range edits, fresh installs, gate runs (lint, test, build), smoke tests, and PR conventions, with a per-dependency risk table for next, react, Auth0, Sentry, tus-js-client, and more. - Pinned exception handling: Documents why ESLint stays capped at 9.x (the scopeManager.addGlobals crash with eslint-config-next) and provides a live smoke test to re-verify before ever bumping. - Drift diagnosis: A workflow for deploys that broke with no code changes — compare resolved versions, reproduce with a fresh install, and pin the culprit to an exact version with a dated removal condition. - Use Case: A Vercel deploy fails on install while CI was green and git log shows no relevant commits; use this Skill to confirm fresh-resolution drift, identify the newly published minor that broke the build, and pin it safely. ## Quick Start Ask the AI to run a dependency currency check on package.json and tell you which packages need a deliberate major bump versus which will self-update.
