skills.rest
yu-iskw
yu-iskwCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

dependency-upgrade

Upgrade outdated dependencies across a pnpm monorepo with recursive updates.

Updated Dec 29, 2025
Search Tags:#workflow#pnpm#monorepo#package.json#upgrade#dependency#lockfile
One-click install
npx skills add https://github.com/yu-iskw/dbt-artifacts-parser-ts --skill dependency-upgrade-yu-iskw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dependency-upgrade
Source: https://github.com/yu-iskw/dbt-artifacts-parser-ts/tree/main/.claude/skills/dependency-upgrade
Command: npx skills add https://github.com/yu-iskw/dbt-artifacts-parser-ts --skill dependency-upgrade-yu-iskw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Upgrading outdated dependencies in a pnpm monorepo is complex and error-prone; this Skill orchestrates a safe, tiered upgrade workflow to keep all workspaces aligned and secure.

Core Features & Use Cases

  • Tiered upgrade strategy: inventory, conservative refresh, targeted upgrades, and explicit consent for aggressive changes.
  • Monorepo-wide dependency management: run commands from the repository root to update all workspaces and refresh the lockfile.
  • Validation gates and post-change checks: lint, coverage, and knip to ensure changes meet quality gates before merging.

Quick Start

Run a conservative update from the repository root to refresh the lockfile and review changes.

Frequently Asked Questions about dependency-upgrade

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

FAQPage Schema
How do I upgrade outdated dependencies across a pnpm monorepo safely?▼

A conservative refresh updates the lockfile and dependencies within existing package.json ranges across all pnpm workspaces, ensuring changes stay within safe boundaries and preventing unintended major version bumps that could break compatibility.

How do I validate dependency upgrades in a pnpm monorepo before merging?▼

You validate pnpm monorepo dependency upgrades by enforcing CI gates that run lint, coverage, and knip checks, ensuring the upgraded workspaces meet quality standards and do not introduce unused code or formatting regressions before merging.

Can I apply aggressive dependency upgrades to all workspaces in a pnpm monorepo?▼

The tiered strategy manages monorepo dependencies by first inventorying outdated packages, then performing a conservative refresh within package.json ranges, executing targeted upgrades for specific packages, and finally requesting explicit consent for aggressive updates.

What is the best way to update the lockfile when upgrading pnpm monorepo dependencies?▼

The best way to update the lockfile is to rely on standard pnpm commands executed from the repository root, which automatically refresh the lockfile and synchronize package versions across all configured workspaces during the upgrade process.

Related Skills

Explore More Software Engineering Skills→
danielctcdanielctc

monorepo-deps

Align dependency versions across pnpm monorepo packages with workspace commands.

Community
Intermediate
axone-protocolaxone-protocol
124

rust-quality-gates

Execute Rust project quality gates for format, lint, tests, coverage, schema, and docs.

Official
Intermediate
RussianLioNRussianLioN
1

setup-knip

Install and configure Knip for dead code detection in JavaScript/TypeScript projects.

Community
Intermediate
MithrilManMithrilMan

gh-release-package

Automate GitHub package releases by bumping package.json and publishing via the Release workflow.

Community
Advanced