Menu
Analyze outdated npm/pnpm dependencies and provide upgrade guidance based on release notes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Implement work from a ticket, spec, or inline description; auto-detects the next item from the task folders when no argument is given.
Show status overview and next steps for an .aiwork/ spec. Use when user says "next steps", "what's left", "status", "progress", or wants to see what's planned, unplanned, or incomplete for a task.
Scan current directory (recursively) for Claude Code skills, slash commands, agents, hooks, and plugin/MCP configs, then render an interactive HTML graph of their explicit and implicit relationships. Use when the user says "skills map", "skill graph", "visualize skills", "map skills", "how do my skills relate", or wants to audit a skill collection before publishing.
Turn the current conversation context into a spec. Use when user wants to create a spec (or PRD) from the current context.
Break a plan, spec, or the current conversation into vertical-slice tickets, each declaring its blocking edges.
Structure AI work artifacts under .aiwork/{YYYY-MM-DD}_{slug}/ folders using the project's protocol (triage, research, spec, prd, plan, review, notes, docs/). Use when the user asks to plan, make a spec, triage, research a task, write a report, code review, summarize findings, save the work, document decisions, record this, write that down, persist findings, or references any path under .aiwork/. Also use when starting a non-trivial task that needs a plan or spec before implementation, or when finishing one and capturing notes.
| name | npm-dep-update |
| description | Analyze outdated npm/pnpm dependencies and provide upgrade guidance based on release notes. |
| allowed-tools | Bash, Read, Write, WebFetch, WebSearch |
Analyze outdated npm/pnpm dependencies, fetch release notes, and produce actionable upgrade guidance.
Output a brief message explaining why before each step (not what - the user sees tool output).
Ask scope before scanning. Detect monorepo via pnpm-workspace.yaml or workspaces in root package.json — if found, recursive is the default.
Ask the user (skip if scope already specified in the request):
deps | devDeps | optional | all (default)yes (all workspaces) | no (current dir)Map answers to script flags:
all → no type flagdeps → -P --type=depsdevDeps → -D --type=devDepsoptional → --type=optional-rOutput: "Checking for outdated dependencies and fetching release notes (this queries npm and GitHub, may take a moment)..."
node "$CLAUDE_SKILL_DIR/scripts/find-release-notes.js" [flags]
Save the output to a file for reference (follow project conventions for artifact storage if any are in context).
Output: "Identifying breaking changes and upgrade risks..." Read the generated file to understand which dependencies need updates.
Based on the release notes content, provide:
If release notes are incomplete for packages with significant version jumps: Output: "Release notes missing for [package] - checking upstream..." Use WebFetch to consult the actual release notes URLs from the generated file.
End with a Suggested upgrade commands section:
vp update pkg1 pkg2 pkg3 (add -r if monorepo recursive)vp update pkg@versionvp run typecheck, vp run test, etc.Skip packages with only patch updates unless they contain security fixes. Focus on actionable guidance. Be concise.