agentleFS
Sign inStart free
MrCipherSmithMrCipherSmith/goodai-base/skills/dependency-update/SKILL.md

dependency-update

Skill0 starsChanged 5 months agoMITView on GitHub

Use when checking for outdated packages or upgrading dependencies with compatibility verification.

  • Installs packages

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use api-design and release.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    api-design

    Guide for designing and documenting RESTful APIs. Use when asked to design an API, create endpoints, or document an API.

    Also in 3 projects that use this

  • MicrosoftSkill

    release

    Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check changelog/migration guide

    line 56
  2. Distinctive:

    Run lint + type-check + tests

    line 58
  3. Distinctive:

    If fails (max 2 fix tries) → rollback

    line 59
  4. Very specific:

    If passes → commit: chore(deps): update <package> to v<version>

    line 60
  5. Distinctive:

    NEVER update all major versions at once — one by one

    line 76
  6. Distinctive:

    ALWAYS run tests after each major update

    line 77
  7. Distinctive:

    Commit each group separately

    line 79
  8. Distinctive:

    Check peer dependency warnings

    line 81

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Dependency Update

Safely update project dependencies with compatibility checks.

Arguments

  • /dependency-update — check and propose updates
  • /dependency-update --patch — only patch updates (safe)
  • /dependency-update --minor — patch + minor
  • /dependency-update --all — all including major
  • /dependency-update --dry-run — show what would update
  • /dependency-update <package> — update specific package

Workflow

Step 1: Check Outdated

npm outdated --json

Step 2: Classify by Risk

TypeRiskAction
Patch (1.0.0 → 1.0.1)LowBatch update
Minor (1.0.0 → 1.1.0)MediumUpdate & test
Major (1.0.0 → 2.0.0)HighOne-by-one with tests

Step 3: Present Update Plan

Show grouped list with risk levels. Get user confirmation.

Step 4: Execute

Patch (batch): npm update

Minor (batch): npm install pkg1@latest pkg2@latest && npm test

Major (one at a time):

  1. Check changelog/migration guide
  2. npm install <package>@latest
  3. Run lint + type-check + tests
  4. If fails (max 2 fix tries) → rollback
  5. If passes → commit: chore(deps): update <package> to v<version>

Step 5: Post-update Verification

npm run lint && npx tsc --noEmit && npm test && npm run build

Step 6: Report

✅ Updated: 15 packages (10 patch, 4 minor, 1 major)
⚠️ Skipped: 2 packages (tests fail)
📋 Commits: 3

Rules

  • NEVER update all major versions at once — one by one
  • ALWAYS run tests after each major update
  • Rollback if tests fail
  • Commit each group separately
  • Respect pinned versions
  • Check peer dependency warnings

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free