agentleFS
mattbutlerengineeringmattbutlerengineering/mattbutlerengineering/.claude/skills/dep-bump/SKILL.md

dep-bump

Skill3 starsChanged 2 days agoMITView on GitHub

Batch-apply pnpm.overrides for CVE fixes in a single PR. Use when multiple Dependabot/security alerts need dependency overrides — collapses N identical workflows into one operation.

  • Installs packages

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If no high-severity vulnerabilities, report clean and stop.

    line 31
  2. Very specific:

    If high-severity vulnerabilities remain, iterate — some CVEs chain (e.g., form-data fixed but tmp still vulnerable).

    line 54
  3. Distinctive:

    If the ratchet shows pre-existing regressions (not from your changes), update the baseline:

    line 62
  4. Very specific:

    Use scoped pattern "pkg@<patched": "^patched" — open ranges pull major bumps

    line 89
  5. Very specific:

    Run pnpm audit --audit-level=high (not --audit-level=moderate) — Build job gates on high only

    line 90
  6. Distinctive:

    Check antipattern baseline — lockfile changes can shift counts

    line 92

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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 Bump (CVE Override Batch)

Apply one or more pnpm.overrides entries to fix CVEs in transitive dependencies, verify the audit passes, and open a single PR.

When to use

  • Multiple Dependabot alerts for transitive dependency CVEs
  • pnpm audit --audit-level=high failing in CI Build job
  • Security issues labeled ready with fix(deps): bump titles

Input

Either:

  • A list of overrides to apply (e.g., from issue bodies)
  • Or no args — the skill scans pnpm audit --audit-level=high and proposes overrides automatically

Workflow

1. Scan for vulnerabilities

pnpm audit --audit-level=high 2>&1

If no high-severity vulnerabilities, report clean and stop.

2. Build override entries

For each vulnerability, construct the scoped override per gotchas:

"pkg@<patched": "^patched"

NOT the open-range form "pkg": ">=patched" — that can pull major bumps.

3. Apply overrides

Edit the pnpm.overrides block in the root package.json. Add new entries; update existing entries if the patched version is higher.

4. Install and verify

pnpm install --lockfile-only
pnpm audit --audit-level=high

If high-severity vulnerabilities remain, iterate — some CVEs chain (e.g., form-data fixed but tmp still vulnerable).

5. Update antipattern baseline

node scripts/check-ai-antipatterns.mjs

If the ratchet shows pre-existing regressions (not from your changes), update the baseline:

node scripts/check-ai-antipatterns.mjs --update

6. Regenerate artifacts

pnpm regen

7. Commit and PR

Stage package.json, pnpm-lock.yaml, any updated baselines, and regenerated artifacts. Commit with:

fix(deps): patch <list of CVEs>

Override <pkg1>@<range> → ^<patched>, <pkg2>@<range> → ^<patched>.
All transitive — no code changes.

Push and open a PR with Closes #<issue1>, Closes #<issue2>, ... for all addressed issues.

Gotchas

  • Use scoped pattern "pkg@<patched": "^patched" — open ranges pull major bumps
  • Run pnpm audit --audit-level=high (not --audit-level=moderate) — Build job gates on high only
  • Regenerate artifacts after lockfile changes — CI "Verify generated artifacts" step will fail otherwise
  • Check antipattern baseline — lockfile changes can shift counts

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.