How do I install the Dependency Update skill?

Run npx skillmds@latest add anchit-choudhry/dependency-update 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 Update 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 Update?

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 Update free to use?

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

Who published Dependency Update?

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

Dependency Update by anchit-choudhry

Name: Dependency Update
Author: anchit-choudhry

Dependency Update

Checks for outdated npm dependencies across the app-drawer workspace (root and packages/express-static-serve), facilitates user-guided updates, and verifies the project still starts cleanly and passes npm audit afterward.

File contents

Dependency Update Skill

Codifies the workflow already described in this repo's CLAUDE.md ("Security & Maintenance") into a repeatable process. Covers the npm workspace as a whole - there is only one package today (express-static-serve), but this runs from the repository root so it picks up new packages under packages/* automatically.

Workflow

Check for updates: Run npm outdated from the repository root.
User review: Present the outdated packages (current, wanted, latest) to the user.
Selection: Ask the user which packages to update and which to skip. Do not upgrade major versions without explicit confirmation, since a major bump can break the Express 5 / express-static-gzip / Helmet integration.
Apply updates: Run npm update <package1> <package2> ... for the selected packages (scoped to the correct workspace if the package isn't at the root).
Audit: Run npm audit. If vulnerabilities remain, run npm audit fix - never npm audit fix --force, per CLAUDE.md.
Verify: Start the server locally (cd packages/express-static-serve && node server.js) and confirm GET / returns { "status": "UP" } before considering the update complete.

Commands

npm outdated: Check for available updates.
npm update [packages...]: Update selected packages.
npm audit: Check for known vulnerabilities.
npm audit fix: Fix vulnerabilities automatically (never with --force).
node packages/express-static-serve/server.js: Verify the server still starts and serves GET / correctly after updates.

Frequently asked questions