Package Update Report

Context

• Lock files: !ls package-lock.json pnpm-lock.yaml yarn.lock 2>/dev/null
• Available scripts: !node -e "const p=require('./package.json');console.log(Object.keys(p.scripts||{}).join(', '))" 2>/dev/null

Workflow

Package Manager Detection

Detect PM from lockfile per CLAUDE.md rules. If no lockfile found, stop and inform user.

Monorepo workspace commands: pnpm --filter {pkg}, npm -w {pkg}, yarn workspace {pkg}

Update Strategy

Investigation Criteria

Sources: GitHub Releases, CHANGELOG.md, official blogs only

Always investigate:

• Major version bumps (breaking changes likely)
• Minor bumps of: frameworks (React, Vue, Next.js), build tools (Vite, esbuild), test tools (Vitest, Jest)

Investigate if verification fails:

• Any package that may be related to the failure

Skip: Patch-only updates with passing verification

Error Handling

• No lockfile found → stop, inform user to run package manager install first
• outdated command returns empty → report "all packages up to date", skip remaining steps
• Verification script not found (e.g., no test script) → skip that check, note in report
• Major update causes verification failure → revert that specific package, note in report as "requires manual migration"

Verification Failure Handling

If verification fails:

1. Identify failing script and error message
2. Search for related packages in the error
3. Investigate those packages' changelogs for breaking changes
4. Document findings in report under "Verification Results"
5. Set conclusion to "Needs attention" with specific action items