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
- sunholo-data/ailangtheir own version, first seen Nov 13, 2026
- fritzprix/libr-agenttheir own version, first seen Nov 10, 2026
- tanbro/uiautomator2-mcp-servertheir own version, first seen Nov 1, 2026
- hongphuc5497/skillstheir own version, first seen Nov 1, 2026
- thefrederiksen/devthrottletheir own version, first seen Nov 1, 2026
- LazyIsEfficient/agentic-ostheir own version, first seen Oct 22, 2026
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.
arnaudgelasSkillqa-agent
Answer questions from the vault, then file durable insights back into the knowledge base.
Also in 3 projects that use this
mar-antayaSkilldependency-auditor
Dependency Auditor
Also in 3 projects that use this
ArogyaReddySkillchangelog-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
MicrosoftSkillplaywright-cli
Automate browser interactions, test web pages and work with Playwright tests.
Also in 3 projects that use this
SentrySkillskill-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
GoogleSkillgrill-me
A relentless interview to sharpen a plan or design.
Also in 3 projects that use this
Other versions27 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 27
- voidzero-dev/vite-plus★ 6.6ksame name
- poingstudios/godot-admob-plugin★ 648same name
- thefrederiksen/cc-director★ 110same name
- thefrederiksen/devthrottle★ 110same name
- LongNgn204/local-coding-agent★ 56same name
- Agile-V/agile_v_skills★ 54same name
- tanbro/uiautomator2-mcp-server★ 54same name
- sunholo-data/ailang★ 38same name
- felvieira/claude-skills-fv★ 28same name
- sampleXbro/agentsmesh★ 27same name
17 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- github-issue-managerSkill
- git-workflow-lifecycleSkill
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
- Distinctive: line 18
Run the preparation script from the repo root:
- Distinctive: line 41
After the Git tag, GitHub release, and optional tap update exist, run:
- Very specific: line 62
Use this skill for the current repo’s manual release model only.
- Very specific: line 63
Prefer running prepare_release.py first and reading its generated checklist before creating tags or GitHub releases.
- Very specific: line 64
If networked gh or brew steps cannot be completed in the current environment, report the exact generated follow-up tasks to the user …
- Distinctive: line 78
If the evaluation fails, fix the scripts or instructions and re-run the evaluation before handing the work back.
“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.
Files
Release Manager
This skill automates the current margo release flow around:
scripts/release.shscripts/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.1This script:
- validates the requested version
- checks the local git state
- runs
go test ./...with a repo-localGOCACHE - 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-margoThis script:
- re-validates the built archives
- verifies the GitHub release via
ghwhen available - checks that the tap formula points at the expected tag and has a non-placeholder checksum
- runs
brew installorbrew upgrade --build-from-source, thenbrew test, andbrew audit --strictusing 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-coresteps unless the repo docs change. - Prefer running
prepare_release.pyfirst and reading its generated checklist before creating tags or GitHub releases. - If networked
ghorbrewsteps 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.pyRead:
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.
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
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.

