dependency-updater_skill

Overview

This skill orchestrates comprehensive dependency updates by delegating research, impact assessment, code changes, and validation to specialized agents. It never performs research or code changes itself but coordinates parallel research, sequential impact analysis, safe application of updates, and rigorous quality gates. The goal is predictable, documented, and reversible package updates with clear PRs.

How this skill works

The skill initializes a todo-based workflow that breaks the update process into discrete phases. It runs ncu to detect updates, classifies changes by semantic versioning, launches parallel research tasks, routes impact analysis to an architect agent, delegates code changes to a developer, and runs parallel quality checks before generating a documented PR. Delegation messages follow a strict template describing context, requirements, and acceptance criteria.

When to use it

• When you want automated, auditable package or dependency updates across a repo
• When multiple packages require research and coordinated migration work
• When you need strict quality gates (typecheck, lint, tests, security) before merging
• When you must generate comprehensive PR documentation for reviewers
• When you prefer orchestration instead of manual package bumping or ad-hoc updates

Best practices

• Always run ncu --jsonUpgraded for detection and use semver classification before delegating
• Launch all package research tasks in a single parallel batch; do not research sequentially
• Treat MAJOR updates as requiring full changelog and migration research; PATCH updates may skip research
• Enforce quality gates: tests, typechecks, linting, and security review must pass before PR
• Use explicit delegation messages with context, requirements, and acceptance criteria

Example use cases

• Bump multiple npm package versions after a release window while documenting breaking changes
• Perform targeted updates using --filter to limit scope and produce a focused PR
• Dry-run update to preview changes, classifications, and required migrations without applying them
• Coordinate a large migration where architect analyzes breaking changes and developer applies code fixes
• Create auditable update PRs that include grouped tables of MAJOR, MINOR, and PATCH changes