skills.rest
davidsneighbour
davidsneighbourCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

manage-node-version-policy

Audits and updates Node.js and npm version declarations across a repository against the official release lifecycle.

1|Updated Aug 18, 2026
Search Tags:#npm#github actions#nodejs#repository maintenance#engines#LTS#version policy
One-click install
npx skills add https://github.com/davidsneighbour/clerkwork --skill manage-node-version-policy-davidsneighbour
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: manage-node-version-policy
Source: https://github.com/davidsneighbour/clerkwork/tree/main/skills/manage-node-version-policy
Command: npx skills add https://github.com/davidsneighbour/clerkwork --skill manage-node-version-policy-davidsneighbour

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repositories accumulate stale, inconsistent Node.js and npm version declarations across package.json engines, .nvmrc, GitHub Actions workflows, Dockerfiles, and documentation, often pinning EOL releases or installing npm@latest in CI. This Skill audits every declaration, aligns them with an explicit LTS or active-latest support policy, and adds a weekly check so versions never silently drift again. ## Core Features & Use Cases - Full-repository version audit: Scans package.json engines, packageManager, version manager files (.nvmrc, .node-version, .tool-versions), GitHub Actions setup-node matrices, Dockerfiles, and docs for Node.js and npm declarations. - Lifecycle-driven policy enforcement: Fetches the official Node.js Release schedule.json to select the latest active LTS or latest active release, computes a bounded engines.node range, and removes unsafe npm@latest CI upgrades. - Weekly drift detection: Adds a check-node-version-policy workflow and a scripts/check-node-version-policy.mjs tool with --check, --write, and --format=json modes, plus optional GitHub issue tracking. - Use Case: A maintainer notices CI still tests Node 18 after its end-of-life. Run the skill in review mode to see each stale declaration with current and proposed values, approve the changes, and let it add the weekly workflow so the next EOL transition is caught automatically. ## Quick Start Use the manage-node-version-policy skill to audit this repository's Node.js and npm version declarations and align them with the latest active LTS release.

Frequently Asked Questions about manage-node-version-policy

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

FAQPage Schema
How do I update Node.js versions across package.json and GitHub Actions?▼

Run this skill to audit engines.node, .nvmrc, setup-node workflow versions, and Dockerfiles, then align them with the latest active LTS or current release. Review mode shows each proposed change for approval; execute mode applies all changes and runs validation.

What Node.js version should my package.json engines field declare?▼

For applications, use a bounded range like ^24.0.0 targeting one selected release. For libraries, include all actively maintained LTS majors, such as ^22.0.0 || ^24.0.0, and avoid unbounded ranges like >=24.0.0 that claim untested future compatibility.

Why is installing npm@latest in CI unsafe?▼

npm@latest is a moving dependency whose Node.js engine requirements can change independently of your repository, breaking builds unexpectedly. Use the npm version bundled with your selected Node.js release, or pin an exact version in packageManager and install that explicitly.

Does this skill support both LTS and Current Node.js releases?▼

Yes, it supports two policies: lts selects the newest major with active LTS status, while active-latest selects the newest released major including odd-numbered Current releases. The policy is read from repository configuration or asked explicitly before changes.

How can I detect stale Node.js versions automatically in CI?▼

The skill adds a weekly GitHub Actions workflow and a scripts/check-node-version-policy.mjs tool that fetches the official release schedule, compares declared versions, and fails when declarations are stale. It can optionally maintain a single tracking issue.

What happens if the Node.js release schedule cannot be fetched?▼

The skill does not guess release status when the lifecycle source is unreachable. It reports the retrieval failure, leaves existing versions unchanged, and explains how to retry, preventing incorrect downgrades or upgrades.

Related Skills

Explore More Software Engineering Skills→
bmad-code-orgbmad-code-org
52.5k

bmad-project-context

Creates and maintains verified AGENTS.md instruction blocks for AI coding agents in a repository.

Official
Advanced
corbat-techcorbat-tech
1

release-pr

Create release pull requests and tags by analyzing conventional commit messages.

Official
Advanced
wesleyosantos91wesleyosantos91
6

dependency-upgrade

Upgrade software dependencies with per-commit testing and vulnerability checks.

Community
Intermediate
ray-manalotoray-manaloto
1

mise-migrate-from-nvm

Migrate Node version management from nvm to mise while preserving pinned versions.

Official
Intermediate