メニュー
Safely upgrade Node.js dependencies in pnpm workspaces. Use when asked to "upgrade dependencies", "update packages", "check for updates", or fix version mismatches.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | node-upgrade |
| description | Safely upgrade Node.js dependencies in pnpm workspaces. Use when asked to "upgrade dependencies", "update packages", "check for updates", or fix version mismatches. |
This skill provides a structured process for safely upgrading Node.js dependencies, ensuring project stability through pre-upgrade health checks and post-upgrade validation.
Before making any changes, verify the current state of the project:
pnpm audit.pnpm test.package.json and the lockfile: cp pnpm-lock.yaml pnpm-lock.yaml.bak.Choose the appropriate upgrade path based on the user's request. Refer to ../common-references/pnpm-commands.md for pnpm-specific commands.
Use this when the user specifies a package or a small set of packages.
pnpm update <package>).package.json to ensure the version has been updated.Use this for general dependency maintenance.
pnpm update).After the upgrade, ensure the project remains stable by delegating to the project verifier:
verifier subagent (../../agents/verifier.md) to run the full build, lint, and test cycle.verifier reports persistent issues it cannot fix, analyze the breaking changes and apply manual fixes or roll back.pnpm audit again to ensure no new vulnerabilities were introduced.package.json and lockfile.
chore(deps): upgrade dependenciesrm *.bak.If validation fails and cannot be easily fixed:
mv package.json.bak package.json and mv <lockfile>.bak <lockfile>.pnpm install to restore the environment.Consistently bump and synchronize versions across all packages in the monorepo using pnpm. Use this to ensure the root and all workspace packages share the same version number.
Run comprehensive integration tests using real skills (Vercel, Anthropic, Expo) in a Docker container. Managed via Makefile for standard lifecycle control.
Synchronize technical sections in README.md and CONTRIBUTING.md with the actual project state.
Run linters and fix violations, formatting errors, or style mismatches using Trunk. Use when code quality checks fail, before submitting PRs, or to repair "broken" linting states.
Build the project and automatically fix any build errors, compilation failures, or type mismatches. Use when the project fails to build, shows "broken" states, or after making significant changes.
Perform a "hard reset" of the development environment. Use when dependencies are corrupted, lockfiles are out of sync, or environment tools (Trunk/pnpm) are in an inconsistent state.