dependency-maintenance

Inspect, update, audit, and validate npm dependencies in single-package repositories and monorepos.

1|Updated Aug 18, 2026
One-click install
npx skills add https://github.com/davidsneighbour/clerkwork --skill dependency-maintenance-davidsneighbour
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dependency-maintenance
Source: https://github.com/davidsneighbour/clerkwork/tree/main/skills/dependency-maintenance
Command: npx skills add https://github.com/davidsneighbour/clerkwork --skill dependency-maintenance-davidsneighbour

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires npm-check-updates.

What problem does it solve? Updating npm dependencies often mixes unrelated changes, breaks builds, or applies risky major upgrades without review. This Skill runs a controlled maintenance workflow that protects existing work, scopes updates, applies safe audit fixes, validates the repository, and optionally creates a conventional commit. ## Core Features & Use Cases - Scoped dependency updates: Applies patch and minor updates by default with npm-check-updates, and requires explicit approval before major upgrades. - Safe audit remediation: Runs npm audit with dry-run inspection, applies only non-breaking fixes, and reports remaining vulnerabilities with recommended actions. - Worktree protection and validation: Detects pre-existing changes, stashes unrelated work when authorized, synchronizes with upstream via fast-forward only, and runs the repository's test, lint, typecheck, and build scripts before committing. - Use Case: Ask the assistant to update outdated packages in an npm workspaces monorepo; it refreshes the root lockfile, fixes safe audit findings, runs validation, and commits with a build(deps) Conventional Commit. ## Quick Start Use the dependency-maintenance skill to inspect outdated packages, apply safe updates, fix audit findings, and validate this repository.

Frequently Asked Questions about dependency-maintenance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely update npm dependencies in a monorepo?▼

Run npm-check-updates from the repository root so workspace manifests and the root lockfile update together. Apply patch and minor updates by default, review major upgrades separately, then run the repository's test, lint, and build scripts before committing.

How to fix npm audit vulnerabilities without breaking changes?▼

Run npm audit fix --dry-run first to inspect the proposed remediation. Apply npm audit fix only when changes are non-breaking and within the approved scope, and never use --force without explicit approval since it can introduce major upgrades.

Does this workflow support pnpm, Yarn, or Bun projects?▼

No, the workflow supports npm projects only. It stops when it detects pnpm-lock.yaml, yarn.lock, or bun.lock files, or when multiple package-manager lockfiles create an ambiguous state, unless the user explicitly asks to adapt the workflow.

What happens to uncommitted changes during dependency updates?▼

The workflow stops if package manifests or lockfiles already have changes and asks how to proceed. Unrelated tracked changes are preferably committed or stashed first; auto-stashing occurs only for authorized automated runs and is never popped automatically.

When are major dependency upgrades applied?▼

Major upgrades are never applied by default on a generic update request. They are presented for review first and applied only when the user explicitly asks for all or latest dependencies or clearly authorizes major version bumps.

Why does dependency maintenance stop before committing?▼

It stops when validation scripts fail, the branch has diverged from upstream, or audit fixes changed files outside the approved scope. The dependency changes are preserved for inspection along with exact rollback commands.