agentleFS
jjanuszczakjjanuszczak/margo/skills/release-manager/SKILL.md

release-manager

Skill2 starsChanged 17 days agoApache-2.0View on GitHub

Prepare and package a new margo release, generate any required follow-on tasks for tagging, GitHub releases, and Homebrew tap updates, and automate verification of the finished release. Use when shipping a new version or validating that a published release is installable.

  • Installs packages

27 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use qa-agent, dependency-auditor and 4 more.

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

    qa-agent

    Answer questions from the vault, then file durable insights back into the knowledge base.

    Also in 3 projects that use this

  • mar-antayaSkill

    dependency-auditor

    Dependency Auditor

    Also in 3 projects that use this

  • ArogyaReddySkill

    changelog-generator

    Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

    Also in 3 projects that use this

  • MicrosoftSkill

    playwright-cli

    Automate browser interactions, test web pages and work with Playwright tests.

    Also in 3 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 4 projects that use this

  • GoogleSkill

    grill-me

    A relentless interview to sharpen a plan or design.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 3

    Distinctive

    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:

    Run the preparation script from the repo root:

    line 18
  2. Distinctive:

    After the Git tag, GitHub release, and optional tap update exist, run:

    line 41
  3. Very specific:

    Use this skill for the current repo’s manual release model only.

    line 62
  4. Very specific:

    Prefer running prepare_release.py first and reading its generated checklist before creating tags or GitHub releases.

    line 63
  5. Very specific:

    If networked gh or brew steps cannot be completed in the current environment, report the exact generated follow-up tasks to the user …

    line 64
  6. Distinctive:

    If the evaluation fails, fix the scripts or instructions and re-run the evaluation before handing the work back.

    line 78

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

Release Manager

This skill automates the current margo release flow around:

  • scripts/release.sh
  • scripts/homebrew-source-sha.sh
  • the personal tap model documented in docs/HOMEBREW.md

Workflow

1. Prepare A Release

Run the preparation script from the repo root:

python3 skills/release-manager/scripts/prepare_release.py 0.1.1

This script:

  • validates the requested version
  • checks the local git state
  • runs go test ./... with a repo-local GOCACHE
  • builds release archives with scripts/release.sh
  • smoke-tests each built archive by extracting it and running margo version
  • writes a release manifest and a follow-up checklist under dist/release/release-<version>/

Optional flags:

  • --allow-dirty: continue even if the worktree is dirty
  • --skip-go-test: skip the full Go test suite
  • --tap-path /path/to/homebrew-margo: include tap-specific follow-up instructions

2. Verify The Finished Release

After the Git tag, GitHub release, and optional tap update exist, run:

python3 skills/release-manager/scripts/verify_release.py 0.1.1 --tap-path /path/to/homebrew-margo

This script:

  • re-validates the built archives
  • verifies the GitHub release via gh when available
  • checks that the tap formula points at the expected tag and has a non-placeholder checksum
  • runs brew install or brew upgrade --build-from-source, then brew test, and brew audit --strict using the tap-qualified formula name when a tap checkout is available

Useful flags:

  • --skip-gh-release-check
  • --skip-brew
  • --brew-formula jjanuszczak/margo/margo

Instructions

  • Use this skill for the current repo’s manual release model only. Do not introduce bottles, GoReleaser, or homebrew-core steps unless the repo docs change.
  • Prefer running prepare_release.py first and reading its generated checklist before creating tags or GitHub releases.
  • If networked gh or brew steps cannot be completed in the current environment, report the exact generated follow-up tasks to the user instead of paraphrasing them loosely.

Self-Evaluation

You MUST verify the skill after changing it:

python3 skills/release-manager/evals/runner.py

Read:

  • skills/release-manager/evals/reports/latest_results.json

If the evaluation fails, fix the scripts or instructions and re-run the evaluation before handing the work back.

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.