mcpField
U
upgrade-js-deps

upgrade-js-deps

github.com/saaspegasusDevelopment32239 installsUpdated 12w ago
Repository

About upgrade-js-deps

A development skill that guides JavaScript dependency upgrades and project verification. It updates package.json, installs packages, then runs type checks, a build, and tests in sequence, stopping and reporting if a step fails.

Key features

  1. 01Check for available dependency upgrades
  2. 02Update versions in package.json
  3. 03Install packages and update the lockfile
  4. 04Run type checks, build, and tests in sequence
  5. 05Summarize results and ask about committing

Use cases

  1. 01Upgrade a project's JavaScript dependencies
  2. 02Verify types, build, and tests after upgrades
  3. 03Decide whether to commit based on upgrade checks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/saaspegasus/django-skills --skill upgrade-js-deps

After installing, type/upgrade-js-depsin Claude Code to confirm it loaded.

Details

From the project README

Your task

Upgrade all JavaScript dependencies and verify nothing is broken.

Step 1: Check for available upgrades

Run npx npm-check-updates to see what upgrades are available. Review the output and present the list to the user.

Step 2: Update package.json

Run npx npm-check-updates -u to update package.json with the new versions.

Step 3: Install updated dependencies

Run make npm-install to install the upgraded dependencies and update package-lock.json.

Step 4: Run post-upgrade checks

Run these checks sequentially, stopping if any step fails:

  1. TypeScript type checking: Run make npm-type-check and report any new type errors.
  2. Build: Run make npm-build to verify the production build still works.
  3. Tests: Run make test to verify the test suite still passes.
Step 5: Summarize and commit

Summarize what was done:

  • Which packages were upgraded (notable version changes)
  • Whether any type errors were introduced
  • Whether the build succeeded
  • Whether all tests passed
  • Any issues that need manual attention

If there were failures, present the issues and ask how the user wants to proceed.

If everything passed, ask the user if they'd like to commit the changes. If yes, commit using the /commit skill.

Comments

Markdown supported