agentleFS
Sign inStart free
matthewwong525matthewwong525/WongStack/.agents/skills/update-dependencies/SKILL.md

update-dependencies

Skill7 starsChanged 11 days agoMITView on GitHub

Update this repo's toolchain and app dependencies, only when asked.

20 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    needs you:: ask first, per required tools.

    line 16
  2. Very specific:

    major:: read the linked notes and migrate.

    line 17

“Common” is measured: kept by at least 6 in 10 of the 20 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

/update-dependencies

This skill is meta-repo only: it is absent from the payload inventory, so no target gets it, and editing only it is no payload release. Run it on demand, never on a schedule.

Run the script

Run node .claude/skills/update-dependencies/scripts/update.mjs and watch its log; in Claude Code, start it in the background. It surveys every tool, app/, scripts/tests/, and site/, updates what is behind, majors too, and moves every OpenSpec pin together; update-dependencies.test.mjs fails, naming the file, when one pin differs. Act on its lines:

  • FAIL: fix what it names, then rerun; finished stages report current.
  • needs you:: ask first, per required tools.
  • major:: read the linked notes and migrate. One you can't: restore its old range and rerun with --hold <package>; name it in the report.
  • openspec:: the contract test ran. Check the release notes against the shared contract and adapt the owning WongStack skill; never accept a missing field silently. No generated layer exists: never run openspec update or regenerate openspec-* skills.
  • status: current: say so and stop without /save.

Payload files changed → follow the release rule; otherwise say why no release is due.

Hand off

Pass a nonempty diff to /save; the change loop owns git and the gate. Fix what CI catches, and never claim green CI proves every major safe. Report what moved, each major's migration or hold, the contract result, and the checks CI ran.

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