agentleFS
Sign inStart free
randommoniclerandommonicle/claude-skills/dependency-upgrade-verification/SKILL.md

dependency-upgrade-verification

Skill27 starsChanged 18 days agoApache-2.0View on GitHub

When a dependency major-bump could silently change on-disk formats or behaviour and runtime data cannot distinguish success from failure, answer the question from the dependency's own source: npm pack both versions and diff the file that decides the behaviour, offline, before hunting for a device repro. Triggers on major version bumps of storage, crypto, or serialisation dependencies. Does not fire on minor or patch bumps, or majors with no storage/serialisation surface.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When runtime evidence cannot distinguish "upgrade handled correctly" from "silently started fresh" (or any two hypotheses about a major …

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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-upgrade verification

A SQLite plugin jumped two majors and the question was whether existing on-device databases would survive. Inspecting runtime data could not answer it: an idempotent initialiser makes a fresh database indistinguishable from a correctly-upgraded one. The data could not distinguish the hypotheses, so no amount of device testing would.

The rule

When runtime evidence cannot distinguish "upgrade handled correctly" from "silently started fresh" (or any two hypotheses about a major bump), move upstream to something the failure cannot forge — the dependency's own published source:

npm pack package@old package@new
# unpack both, diff the file that decides the behaviour

Diff the specific file that implements the concern (the storage layer, the migration handler, the serialisation format), offline, before hunting for a device repro. The tarballs are free, authoritative, and available without a device.

Why

Published tarballs are a first-class diagnostic that answers in minutes what black-box testing cannot answer at all when the observable states are identical. Evidence: ASH LESSONS_LEARNED 2026-07-20 (SQLite plugin 6 to 8).

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