How do I install the Dependency Upgrade skill?

Run npx skillmds@latest add tomevault-io/dependency-upgrade-4 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Dependency Upgrade safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dependency Upgrade?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dependency Upgrade free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dependency Upgrade?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dependency Upgrade by tomevault-io — Agent Skill

Name: Dependency Upgrade
Author: tomevault-io

Dependency Upgrade

Upgrade dependencies safely using pnpm catalog, checking for breaking changes, and testing upgrades. Use when updating packages, applying security patches, upgrading major versions, resolving dependency conflicts, or modernizing tech stack. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Dependency Upgrade Skill

Uses pnpm with catalog for centralized dependency management.

Check for Updates

pnpm outdated                      # Check all outdated
pnpm -r outdated                   # Across workspace
pnpm -F @sgcarstrends/api outdated # Specific package
pnpm dlx taze --interactive        # Interactive upgrade

Upgrade Process

1. Update Catalog

# pnpm-workspace.yaml
catalog:
  next: ^16.0.0  # Upgraded from ^15.0.0
  react: ^19.0.0

Packages reference with "package": "catalog:" in package.json.

2. Install and Test

pnpm install
pnpm tsc --noEmit  # Type check
pnpm test          # Unit tests
pnpm biome check . # Lint
pnpm build         # Build
pnpm dev           # Manual testing

3. Fix Breaking Changes

// Example: Next.js 16 async params
// Before
export default function Page({ params }: { params: { id: string } }) {
  return <div>{params.id}</div>;
}

// After
export default async function Page({ params }: { params: Promise<{ id: string }> }) {
  const { id } = await params;
  return <div>{id}</div>;
}

4. Commit

git commit -m "chore(deps): upgrade Next.js to v16

- Upgrade Next.js 15 → 16
- Upgrade React 18 → 19
- Fix async params migration

BREAKING CHANGE: Requires Node.js 20+"

Major Version Upgrades

Next.js

pnpm dlx @next/codemod@latest upgrade latest  # Run codemod
# Update catalog: next: ^16.0.0, react: ^19.0.0
pnpm install
# Fix: async params, async cookies/headers

TypeScript

# Update catalog: typescript: ^5.3.3
pnpm install
pnpm tsc --noEmit  # Fix type errors

Drizzle ORM

# Update catalog: drizzle-orm: ^0.30.0, drizzle-kit: ^0.20.0
pnpm install
pnpm -F @sgcarstrends/database db:generate  # If schema changed

Security Updates

pnpm audit                 # Check vulnerabilities
pnpm audit --fix           # Auto-fix
# Or manually update vulnerable package in catalog

Dependency Conflicts

pnpm why package-name      # Check dependency chain
pnpm dedupe                # Deduplicate

Use overrides as last resort:

{ "pnpm": { "overrides": { "react": "^19.0.0" } } }

Rollback

git reset --hard HEAD
# Or revert lockfile:
git checkout main -- pnpm-lock.yaml
pnpm install

Troubleshooting

# Lockfile conflicts
rm pnpm-lock.yaml && pnpm install

# Build failures after upgrade
rm -rf node_modules .turbo dist .next && pnpm install && pnpm build

Best Practices

Use Catalog: Centralize versions in pnpm-workspace.yaml
Test Thoroughly: Run all tests after upgrades
Read Changelogs: Review breaking changes before upgrading
Upgrade Incrementally: Don't update everything at once
Commit Separately: Separate dependency upgrades from features
Automate Security: Use Dependabot for security patches

References

pnpm Catalog: https://pnpm.io/catalogs
Next.js Codemods: https://nextjs.org/docs/app/building-your-application/upgrading/codemods
See security skill for vulnerability scanning

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: dependency-upgrade-4description: Upgrade dependencies safely using pnpm catalog, checking for breaking changes, and testing upgrades. Use when updating packages, applying security patches, upgrading major versions, resolving dependency conflicts, or modernizing tech stack. Use when this capability is needed.---# Dependency Upgrade SkillUses **pnpm with catalog** for centralized dependency management.## Check for Updates```bashpnpm outdated # Check all outdatedpnpm -r outdated # Across workspacepnpm -F @sgcarstrends/api outdated # Specific packagepnpm dlx taze --interactive # Interactive upgrade```## Upgrade Process### 1. Update Catalog```yaml# pnpm-workspace.yamlcatalog: next: ^16.0.0 # Upgraded from ^15.0.0 react: ^19.0.0```Packages reference with `"package": "catalog:"` in package.json.### 2. Install and Test```bashpnpm installpnpm tsc --noEmit # Type checkpnpm test # Unit testspnpm biome check . # Lintpnpm build # Buildpnpm dev # Manual testing```### 3. Fix Breaking Changes```typescript// Example: Next.js 16 async params// Beforeexport default function Page({ params }: { params: { id: string } }) { return <div>{params.id}</div>;}// Afterexport default async function Page({ params }: { params: Promise<{ id: string }> }) { const { id } = await params; return <div>{id}</div>;}```### 4. Commit```bashgit commit -m "chore(deps): upgrade Next.js to v16- Upgrade Next.js 15 → 16- Upgrade React 18 → 19- Fix async params migrationBREAKING CHANGE: Requires Node.js 20+"```## Major Version Upgrades### Next.js```bashpnpm dlx @next/codemod@latest upgrade latest # Run codemod# Update catalog: next: ^16.0.0, react: ^19.0.0pnpm install# Fix: async params, async cookies/headers```### TypeScript```bash# Update catalog: typescript: ^5.3.3pnpm installpnpm tsc --noEmit # Fix type errors```### Drizzle ORM```bash# Update catalog: drizzle-orm: ^0.30.0, drizzle-kit: ^0.20.0pnpm installpnpm -F @sgcarstrends/database db:generate # If schema changed```## Security Updates```bashpnpm audit # Check vulnerabilitiespnpm audit --fix # Auto-fix# Or manually update vulnerable package in catalog```## Dependency Conflicts```bashpnpm why package-name # Check dependency chainpnpm dedupe # Deduplicate```Use overrides as last resort:```json{ "pnpm": { "overrides": { "react": "^19.0.0" } } }```## Rollback```bashgit reset --hard HEAD# Or revert lockfile:git checkout main -- pnpm-lock.yamlpnpm install```## Troubleshooting```bash# Lockfile conflictsrm pnpm-lock.yaml && pnpm install# Build failures after upgraderm -rf node_modules .turbo dist .next && pnpm install && pnpm build```## Best Practices1. **Use Catalog**: Centralize versions in pnpm-workspace.yaml2. **Test Thoroughly**: Run all tests after upgrades3. **Read Changelogs**: Review breaking changes before upgrading4. **Upgrade Incrementally**: Don't update everything at once5. **Commit Separately**: Separate dependency upgrades from features6. **Automate Security**: Use Dependabot for security patches## References- pnpm Catalog: https://pnpm.io/catalogs- Next.js Codemods: https://nextjs.org/docs/app/building-your-application/upgrading/codemods- See `security` skill for vulnerability scanning---> Converted and distributed by [TomeVault](https://tomevault.io/claim/sgcarstrends) — claim your Tome and manage your conversions.

Frequently asked questions