agentleFS
bastyn-labsbastyn-labs/bastyn-scan/.agents/skills/verify-release/SKILL.md

verify-release

Skill2 starsChanged 27 days agoApache-2.0View on GitHub

Check that a Bastyn release vX.Y.Z is published in all four places (git tag, GitHub release, crates.io, Homebrew tap). Use when asked whether a release is tagged, published or live. Read-only; reports PASS or FAIL per check.

16 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 16 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:

    Run the script with the version, with or without the leading v:

    line 9
  2. Very specific:

    Only final vMAJOR.MINOR.PATCH tags are accepted.

    line 31

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

Verify a release

Run the script with the version, with or without the leading v:

.agents/skills/verify-release/scripts/verify-release.sh v0.8.0

It runs four checks and prints PASS or FAIL for each, then a RESULT line.

CheckPasses when
git tagrefs/tags/vX.Y.Z exists on BASTYN-labs/bastyn-scan
github releasethe release is not a draft and has five platform archives, each with a .sha256
crates.iothe bastyn crate has version X.Y.Z and it is not yanked
homebrewFormula/bastyn.rb in BASTYN-labs/homebrew-tap names vX.Y.Z for the four macOS and Linux targets

The release counts as published only when all four pass. Exit codes: 0 all passed, 1 at least one failed, 2 bad argument or missing tool.

Report the script's output as it is. Do not infer a pass for a check that failed or did not run.

Notes

  • The crate is bastyn. bastyn-cli is a placeholder that stays at 0.1.0.
  • Only final vMAJOR.MINOR.PATCH tags are accepted. A release candidate updates GitHub Releases only, so the crates.io and Homebrew checks do not apply to it.
  • Windows is in the release archives but not in the Homebrew formula.
  • The script never tags, publishes or writes anything. How a release is cut is in CONTRIBUTING.md under "Releasing".

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.