Update dependencies

Treat dependency maintenance as a sweep: inventory owned version declarations, let the repository's package manager resolve the package graph, then validate and account for the result.

Invoke with /update-dependencies Update dependencies for a repository or its entire monorepo. Add and open a pull request to publish, or request an audit, selected packages, or latest major versions to change the scope. Infer workspace coverage from the repository.

Infer the authorization mode from the request:

Audit: inventory and assess updates without changing files.
Improve: the default; apply policy-compatible updates, validate them, and leave the result uncommitted.
Publish: improve, then perform the requested publication. A pull-request request includes the branch, commit, and push needed to create it.

Repository instructions, manifests, and maintenance configuration own project policy. This skill supplies the process around them. When applicable authorities disagree and current repository evidence does not resolve the conflict, hold the disputed update and continue with unambiguous work.

1. Establish the maintenance contract

Resolve the Git root, current branch, worktree status, and every package-manager root inside the repository. Read applicable AGENTS.md and equivalent instructions from broadest to narrowest scope, then follow their routes to dependency, security, release, CI, generated-code, and validation guidance.

For each package-manager root, identify the manager and version from its declaration and lockfile. Record workspace boundaries, required scripts, update automation, version-range and peer policy, patched or generated artifacts, toolchain declarations, default branch, and publication rules. Use the repository's manager and version for resolution and validation.