菜单
Use when updating major Node.js versions across ng-mocks projects, including CI/CD, .nvmrc, Docker images, npm compatibility, @types/node, and wrapper-based validation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when refreshing package-lock.json files in ng-mocks.
Use when preparing GitHub Dependabot pull requests by listing open PRs, verifying they are authored by app/dependabot, enabling auto-merge, and approving them without merging manually.
Use when replaying the current local branch onto upstream/main, or onto another provided remote branch, by stashing local changes, resetting to the target branch, and cherry-picking missing commits back one by one.
Use when triaging or fixing ng-mocks GitHub issues and bug reports in a dedicated worktree based on upstream/main, with a local issue-* regression test, a focused source fix, coverage validation, e2e matrix checks, a conventional commit message, and a pull request.
Use when syncing or simplifying example code in docs/articles or README.md so embedded docs samples stay aligned with examples tests while removing compatibility noise from the published snippets.
| name | update-node-version |
| description | Use when updating major Node.js versions across ng-mocks projects, including CI/CD, .nvmrc, Docker images, npm compatibility, @types/node, and wrapper-based validation. |
Use this skill when the request is to update major Node.js version across some or all of the repository.
Begin with a plain Markdown checklist that works in AI Agent:
- [ ] Identify which projects should move to the new Node line
- [ ] Inspect all current Node, npm, Docker, and type-version declarations
- [ ] Update the affected config and package files together
- [ ] Re-bootstrap dependencies with wrapper commands
- [ ] Run wrapper-based validation on every changed target
- [ ] Summarize the new version mapping and any compatibility limits
.nvmrc, docs/.nvmrc, tests-e2e/.nvmrc, and affected e2e/*/.nvmrccompose.yml.circleci/config.yml and any CI workflow that pins a Node versionpackage.json files.nvmrcnpm versionengines.npm@types/node where applicablesh compose.sh <target>.sh test.sh for root, e2e, and every changed target.update-package-locks skill instead of an ad-hoc npm command.# Bootstrap changed targets with a unique compose namespace.
COMPOSE_PROJECT_NAME=ngmocks_node_<unique> sh compose.sh root
COMPOSE_PROJECT_NAME=ngmocks_node_<unique> sh compose.sh e2e
COMPOSE_PROJECT_NAME=ngmocks_node_<unique> sh compose.sh <target>
COMPOSE_PROJECT_NAME=ngmocks_node_<unique> sh compose.sh docs
# Validate changed targets.
COMPOSE_PROJECT_NAME=ngmocks_node_<unique> sh test.sh root
COMPOSE_PROJECT_NAME=ngmocks_node_<unique> sh test.sh e2e
COMPOSE_PROJECT_NAME=ngmocks_node_<unique> sh test.sh <target>
COMPOSE_PROJECT_NAME=ngmocks_node_<unique> docker compose run --rm docs npm run build
COMPOSE_PROJECT_NAME=ngmocks_node_<unique> sh test.sh rootCOMPOSE_PROJECT_NAME=ngmocks_node_<unique> sh test.sh e2eCOMPOSE_PROJECT_NAME=ngmocks_node_<unique> sh test.sh <target> for each target whose Node line changedCOMPOSE_PROJECT_NAME=ngmocks_node_<unique> docker compose run --rm docs npm run build when the docs Node line changednpm install, npm update, or ad-hoc node commands for validation when wrapper commands exist.COMPOSE_PROJECT_NAME for all commands in the same worktree.chore(docker): updating node images.