agentleFS
torisKRtorisKR/toris-agent/skills/release-check/SKILL.md

release-check

Skill2 starsChanged 4 months agoApache-2.0View on GitHub

Verify a package is actually installable and runnable before publishing or tagging.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use review.

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.
  • SentrySkill

    review

    Fixture review skill.

    Also in 5 projects that use this

The file

Files
SKILL.md

Release check

The bug that survives every test is "it works in the repo but not once installed".

Procedure

  1. Clean state. Confirm the working tree is clean and the branch is pushed.
  2. Pack, do not publish. Build the tarball (npm pack) and inspect the file list. Anything missing from files will be missing for every user.
  3. Install from the tarball into a scratch prefix — never rely on the repo being on disk. Run the binary's --version and one real command.
  4. Check metadata. Version, license, repository URL, and entry points must all resolve. A wrong bin path breaks the install silently.
  5. Only then tag and publish, and record what you verified.

Stop conditions

  • The smoke test fails from the tarball → do not publish, fix packaging first.
  • Version already exists on the registry → stop, publishing is irreversible.

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.