# Dependency Upgrade Demo Dependency Upgrade

> Use when running dependency upgrade workflows for dependency-upgrade-demo.

- Skill: `guorunjie/dependency-upgrade-demo-dependency-upgrade` (Agent Skill)
- Install (CLI): `npx skillmds@latest add guorunjie/dependency-upgrade-demo-dependency-upgrade`
- Raw SKILL.md: https://api.skillmd.com/api/skills/guorunjie/dependency-upgrade-demo-dependency-upgrade/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: guorunjie (https://skillmd.com/u/guorunjie)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/guorunjie/dependency-upgrade-demo-dependency-upgrade

---


# dependency-upgrade-demo-dependency-upgrade

Generated from `skillpack.yaml` by Skillpack Forge.

## Project
Dependency upgrade workflows for reviewing outdated packages, applying safe updates, and verifying compatibility.

## Workflow
- Inspect package manifests, lockfiles, current dependency versions, and available update commands
- Run the narrowest outdated or audit command first, such as npm outdated or npm audit
- Apply patch and minor updates before considering major-version changes
- Review changelog notes, migration guides, and generated lockfile diffs for risky packages
- Run focused verification, then the broader relevant suite, and document any pinned or deferred upgrades

## Commands
- install: `npm install`
- test: `npm test`
- outdated: `npm run outdated`
- deps:check: `npm run deps:check`
- deps:update: `npm run deps:update`
- deps:audit: `npm run deps:audit`

## Principles
- Review changelogs, release notes, and lockfile changes before broad upgrades
- Prefer one dependency group at a time so regressions stay attributable
- Run audit, focused tests, and the relevant full suite before reporting success
- Document skipped major versions, risky transitive changes, and follow-up work