// Safely upgrade Node.js dependencies in pnpm workspaces. Use when asked to "upgrade dependencies", "update packages", "check for updates", or fix version mismatches.
Build the project and automatically fix any build errors, compilation failures, or type mismatches. Use when the project fails to build, shows "broken" states, or after making significant changes.
Run CodeQL security/quality analysis and fix findings. Use when the user asks to run CodeQL, security scan, static analysis, or fix CodeQL findings.
Self-improvement skill for evolving Claude Code configuration. Use when you notice repeated mistakes, want to add new workflows, or optimize the development experience.
Run linters and fix violations, formatting errors, or style mismatches using Trunk. Use when code quality checks fail, before submitting PRs, or to repair "broken" linting states.
End-of-session capture of failures, surprises, and lessons so agent behavior and repo config improve. Use after non-trivial work; skip trivial sessions unless something went wrong.
Scan for vulnerable dependencies and CVEs via pnpm lint:security (Trunk Trivy/OSV-scanner), optional pnpm security:grype or pnpm lint:all (Trunk-all plus Grype). Use for dependency CVE checks, security-scoped lint, or post-bump verification.
| name | node-upgrade |
| description | Safely upgrade Node.js dependencies in pnpm workspaces. Use when asked to "upgrade dependencies", "update packages", "check for updates", or fix version mismatches. |
This skill provides a structured process for safely upgrading Node.js dependencies, ensuring project stability through pre-upgrade health checks and post-upgrade validation.
Before making any changes, verify the current state of the project:
pnpm audit.pnpm test.package.json and the lockfile: cp pnpm-lock.yaml pnpm-lock.yaml.bak.Choose the appropriate upgrade path based on the user's request (for example pnpm update <package> for targeted updates or pnpm update for broader maintenance).
Use this when the user specifies a package or a small set of packages.
pnpm update <package>).package.json to ensure the version has been updated.Use this for general dependency maintenance.
pnpm update).After the upgrade, ensure the project remains stable by delegating to the project verifier:
verifier subagent (see .claude/agents/verifier.md) to run the full build, lint, and test cycle.verifier reports persistent issues it cannot fix, analyze the breaking changes and apply manual fixes or roll back.pnpm audit again to ensure no new vulnerabilities were introduced.package.json and lockfile.
chore(deps): upgrade dependenciesrm *.bak.If validation fails and cannot be easily fixed:
mv package.json.bak package.json and mv <lockfile>.bak <lockfile>.pnpm install to restore the environment.