What problem does it solve? Upgrading a project's Node.js runtime is risky without knowing which release lines are still supported, which dependencies break on newer versions, and what files need updating. This Skill produces a complete, evidence-based upgrade plan so you avoid landing on an EOL version or breaking CI. ## Core Features & Use Cases - Live Release Schedule: Fetches the authoritative Node.js LTS/EOL table from endoflife.date (with an offline fallback) so recommendations never rely on stale training data. - Automatic Version Detection: Reads the current version from package.json engines, .nvmrc, .node-version, or the runtime on PATH, treating project pins as authoritative. - Full Upgrade Guide: Delivers a recommended target version, key changes, step-by-step migration (nvmrc, engines, CI/CD, Docker), dependency compatibility checks via NCM, and verification steps. - Use Case: Your project pins Node 16 in .nvmrc and CI is failing deprecation checks. Ask for an upgrade plan and receive a recommendation for the newest Active LTS, the exact files to change, and how to verify the migration. ## Quick Start Ask the assistant to plan a Node.js upgrade for this project and recommend which LTS version to move to.