dependency-maintenance
Dependency maintenance. Use when adding, moving, or upgrading dependencies, changing pnpm or JavaScript runtimes, updating TypeScript or build/test tools, or changing native-build policy, patches, or test images.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-13
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- dependency-maintenance
- description
- Dependency maintenance. Use when adding, moving, or upgrading dependencies, changing pnpm or JavaScript runtimes, updating TypeScript or build/test tools, or changing native-build policy, patches, or test images.
02 资源文件 2
- 参考文档coordinated-upgrades.md2.5 KB
- 参考文档manifest-roles.md2.1 KB
03 SKILL.md 正文
Treat an upgrade as a synchronization task, not a lockfile refresh. Derive versions, commands, and compatibility points from the current repository.
Discover
- Read affected manifests and scripts,
pnpm-workspace.yaml, setup actions, workflows, test configuration, and compatibility documentation. - Search for the dependency and every current version, range, runtime input, image, engine constraint, patch, and compatibility claim.
- Record each match as a development version, tested version, peer range, engine minimum, advertised minimum, or intentionally different constraint.
- When adding or moving a manifest entry, read manifest-roles.md before selecting its role.
- Select the package-local or coordinated branch and its validation matrix.
Discovery is complete when every match and affected validation surface is accounted for.
Package-local branch
Use this branch only for one dependency in one workspace package when runtime, compiler, package-manager, image, patch, native-build, and shared-tooling policy are unchanged.
Update only the owning manifest and keep peer compatibility independent from the development version tested here. If any coordinated surface appears, switch branches.
This branch is complete when the manifest and lockfile agree, focused checks pass, and every search result is intentionally unchanged or package-local.
Coordinated branch
Read coordinated-upgrades.md, select every applicable row, and update all listed synchronization points before installing. Apply root workflow and generated-file requirements before editing those surfaces, then return here to finish matrix and lockfile review.
Install and finish
Run root pnpm install after all selected edits. Inspect warnings and the
semantic lockfile diff for specifiers, resolutions, duplicate transitives, peer
changes, integrity, patch hashes, lifecycle scripts, and allowBuilds effects.
A successful install alone does not complete this review.
Run the narrowest correctness and performance checks that cover every selected matrix row. Apply the root changeset routing after implementation and focused validation.
The task is complete when repeated repository searches find no unclassified synchronization point, manifest roles and compatibility ranges are intentional, the lockfile has no unexplained churn, and every selected check passes or is reported as not runnable.
04 同仓库更多 Skills
vendored-assets
Vendored assets. Use when importing or updating checked-in third-party or externally generated JavaScript, CSS, registries, schemas, snapshots, or Scalar, Swagger, and MIME artifacts.
test-development
Test development. Use when adding or changing Vitest or Tstyche coverage. Choose Tstyche only for intended compiler behavior such as inference, assignability, rejection, or displayed public types.
pull-requests
Pull request finalization. Use when a change works and is about to be opened as a pull request, or when updating or continuing an existing one.
performance-analysis
Performance analysis. Use for runtime throughput or latency benchmarks, TypeScript compiler cost, performance regressions, comparison harnesses, or thresholds.
package-development
Package registration. Use when adding a workspace package, making a private package publishable, renaming a package, or moving its workspace path.
migration-guidance
Use when changing how a v3 public API maps to v4, editing migration annotations, or regenerating migration/v3-to-v4.md.