dependency-maintenance

Automate dependency maintenance for Vite and pnpm monorepos.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/jkker/maam --skill dependency-maintenance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-maintenance
Source: https://github.com/jkker/maam/tree/main/.agents/skills/dependency-maintenance
Command: npx skills add https://github.com/jkker/maam --skill dependency-maintenance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Routine dependency management across vite+ pnpm monorepo workspaces to keep versions aligned, reduce manual chasing, and improve security posture.

Core Features & Use Cases

  • Catalog-driven version coordination across workspaces
  • Audit fixes, major version migrations, and changelog review
  • Node subpath imports and workspace overrides for reproducible upgrades

Quick Start

Run a full dependency health check and apply safe updates across the workspace.

Frequently Asked Questions about dependency-maintenance

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

FAQPage Schema
How do I automate pnpm monorepo dependency maintenance across all workspaces?

Automating pnpm monorepo dependency maintenance involves applying shared catalogs, managing workspace overrides, and running audits across all workspaces. This reduces manual version chasing and improves security posture.

What is the pnpm catalog protocol and how does it coordinate workspace versions?

The pnpm catalog protocol coordinates dependency versions across a monorepo by referencing a shared catalog. This ensures all workspaces use aligned versions, reducing manual updates and preventing version drift across the vite and pnpm environment.

How do I run a dependency health check and apply safe updates in a vite monorepo?

Running a dependency health check in a vite monorepo applies safe updates by reviewing changelogs and executing structured verification steps. This process covers audit fixes, major version migrations, and Node subpath imports.

Can I manage major version migrations and vulnerability fixes for pnpm workspaces?

Managing major version migrations and vulnerability fixes for pnpm workspaces is supported through structured verification steps. This includes applying workspace overrides for reproducible upgrades and reviewing changelogs to ensure security.

Does this dependency maintenance approach work with Node subpath imports?

Yes, dependency maintenance for pnpm monorepos explicitly handles Node subpath imports. This ensures reproducible upgrades and correct package resolution during major version migrations and vulnerability fixes across all workspaces.

What are the limitations of using catalog-driven dependency management in a monorepo?

Catalog-driven dependency management in a monorepo requires strict adherence to the pnpm catalog protocol and structured verification steps. Limitations arise if workspaces bypass the shared catalog, causing version drift and reducing reproducible upgrade reliability.