← ClaudeAtlas

nodejs-project-upgradelisted

Check for available updates, vulnerabilities and Node.js support status across the Stratcore CodeProjects, then upgrade one project's npm dependencies, Node.js version or Docker base images on an isolated branch with verification. Use when the user says check updates, what's outdated, npm audit, vulnerabilities, upgrade or bump dependencies, upgrade Next.js/React/Node, maintenance pass on <project>, or update base images. Covers GarageERP, StratDesk, Silvaros NLI, DrezuraTop, ParkourTop and MarcelKocian (plus a read-only survey of every other Node repo). Hands releases to vps-container-release.
thestratcore/My-skills · ★ 0 · AI & Automation · score 62
Install: claude install-skill thestratcore/My-skills
# Node.js project upgrade Survey first, then upgrade one project in small verified groups on its own branch, then hand off to `vps-container-release` to release. Projects, their pins and verify commands: [references/projects.md](references/projects.md). `<skill>` below means this skill's folder (`~/.claude/skills/nodejs-project-upgrade`, or the `MySKILLS` copy). ## Hard rules 1. Survey before changing anything. Plan the update groups from the survey. 2. Work in an isolated worktree branched from an explicit revision. Never touch unrelated changes in the main checkout. 3. Use npm, the projects' package manager. Never mix lockfiles, never delete `package-lock.json`, and never use `--force`, `--legacy-peer-deps` or `npm audit fix --force`. 4. One update group per commit. Every major is its own group. 5. A Node version change updates `.nvmrc`/`.node-version`, `engines`, every Dockerfile stage and the CI `node-version` together. 6. Don't change behaviour, schema, authentication, integrations, screenshot baselines or release mode in passing. If an upgrade needs any of that, stop and ask. 7. No push, publish or deploy. Releasing is `vps-container-release`, with its own approval. Pushing Silvaros NLI's `main` **deploys**. 8. Report verified checks separately from assumptions. Zero audit findings does not mean "secure". ## Step 0: triage 1. Find the project in `projects.md`. Read its vault `PROJECT_KNOWLEDGE.md` and the repo's `AGENTS.md`. 2. Pick the mode: - "Check updates",