release
Skill4 starsChanged todayMITView on GitHub
[oh-my-agy] End-to-end release engineering workflow covering pre-release quality gates, SemVer bump classification, CHANGELOG and manifest synchronization, dry-run packaging validation, rollout/rollback playbooks, and tag or registry confirmation gates. Use for $release or when preparing a versioned release, release notes, or production rollout.
- Reads credentials
- Commits and pushes
193 other projects use a version of this.
Adopted by
Most recently taken up by
- yicheng47/runnertheir own version, first seen Nov 13, 2026
- eugene1g/agent-safehousetheir own version, first seen Nov 12, 2026
- BlockRunAI/ClawRoutertheir own version, first seen Nov 11, 2026
- cubeplexai/cubeplextheir own version, first seen Nov 10, 2026
- bex-co/bextheir own version, first seen Nov 10, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 9, 2026
Used with
Projects with it also use create-agent-adapter, changelog-style and 10 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.
MicrosoftSkillcreate-agent-adapter
Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.
Also in 5 projects that use this
GrinvSkillchangelog-style
Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.
Also in 4 projects that use this
GrinvSkilldocs-consistency-check
Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.
Also in 4 projects that use this
Microsoft AzureSkillcomponent-release
Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.
Also in 4 projects that use this
Microsoft AzureSkilldocumentation-consistency
Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.
Also in 8 projects that use this
rivet-devSkilllaunch-graphics
Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.
Also in 3 projects that use this
- +3 more from Grinv
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- paperclipai/paperclip★ 114ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 73ksame name
- traefik/traefik★ 66ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 64ksame name
- amruthpillai/reactive-resume★ 46ksame name
- reactive-resume/reactive-resume★ 46ksame name
- AmruthPillai/Reactive-Resume★ 45ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
183 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 repository23 other files it gives its agents.
- rules/AGENTS.mdAGENTS.md
- ai-slop-cleanerSkill
- analyzeSkill
- askSkill
- autopilotSkill
- cancelSkill
- code-reviewSkill
- deep-interviewSkill
- deep-researchSkill
- doctorSkill
- hudSkill
- loftSkill
- modernizeSkill
- performance-goalSkill
- prSkill
- ralplanSkill
- skillSkill
- teamSkill
- threat-modelSkill
- ultragoalSkill
- ultraqaSkill
- visual-ralphSkill
- wikiSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 0 are distinctive, and 12 are very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Confirmation gate for irreversible actions: never execute git tag, git push, GitHub release creation, or a live npm publish without …
- Very specific: line 22
Zero unverified greenwashing: never bump version manifests or CHANGELOG.md until tests, license checks, doc parity, and floor guards pass …
- Very specific: line 23
No fabricated release metrics or unverified diffs: every item in CHANGELOG.md must come from observed commits, diffs, or verified artifact …
- Very specific: line 27
Run read-only readiness checks in order (delegate to devops-engineer, doc-steward, or supply-chain-auditor for parallel audit/fixes):
- Very specific: line 29
Git hygiene & clean diff: verify working tree expectations (git status --short), ensure zero untracked temp debris, and run sh …
- Very specific: line 30
Test, lint, syntax & host parity suite: run full repo tests, POSIX sh -n syntax checks on launchers, CI build scripts, and host validation …
- Very specific: line 31
Supply-chain & license compliance: run sh <plugin>/hooks/run.sh dep-license-diff <repo> [lastTag] --json and sh <plugin>/hooks/run.sh …
- Very specific: line 32
Documentation & env drift: run sh <plugin>/hooks/run.sh docs-drift <repo> --json and sh <plugin>/hooks/run.sh wiki-lint <wiki> --json …
- Very specific: line 34
If --check is set, stop here with a structured Pass/Fail readiness scorecard.
- Very specific: line 43
Sync Version Across All Declared Sources: update every manifest that declares the version (e.g., plugin.json, package.json, pyproject.toml, …
- Very specific: line 48
Run dry-run artifact packaging cleanly (npm publish --dry-run, tar/zip tarball inspection, or isolated temp-dir host bundle install + …
- Very specific: line 49
Document the rollout and rollback plan (references/rollout-and-compliance.md): canary verification commands, health/smoke probes …
“Common” is measured: kept by at least 6 in 10 of the 183 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
Prepare, verify, and stage a versioned software release cleanly. Unlike $pr (which summarizes branch changes for a pull request review), $release validates cross-repo release readiness, computes SemVer impact, synchronizes version manifests and release notes (CHANGELOG.md), executes dry-run packaging (--dry-run) checks, and assembles an explicit go/no-go release checklist before any irreversible git tag or package publish runs.
Usage
$release "0.8.0"
$release --check "validate release readiness without modifying manifests"
$release --dry-run "prepare bump, changelog, and dry-run bundle validation"Boundaries
- Consult references/rollout-and-compliance.md before classifying breaking changes, publishing artifacts, or staging canary rollbacks.
- Confirmation gate for irreversible actions: never execute
git tag,git push, GitHub release creation, or a livenpm publishwithout explicit user approval in the active turn (avoid running livenpm publishcleanly by validating--dry-runfirst). - Zero unverified greenwashing: never bump version manifests or
CHANGELOG.mduntil tests, license checks, doc parity, and floor guards pass cleanly. - No fabricated release metrics or unverified diffs: every item in
CHANGELOG.mdmust come from observed commits, diffs, or verified artifact outputs in the current workspace.
Pre-Release Readiness Gate
Run read-only readiness checks in order (delegate to devops-engineer, doc-steward, or supply-chain-auditor for parallel audit/fixes):
- Git hygiene & clean diff: verify working tree expectations (
git status --short), ensure zero untracked temp debris, and runsh <plugin>/hooks/run.sh floor-guard <repo> --json(total: 0, zero secrets, disabled tests, or unresolved blockers). - Test, lint, syntax & host parity suite: run full repo tests, POSIX
sh -nsyntax checks on launchers, CI build scripts, and host validation (skill-validate --strict,host-validate --strictwhen shipping plugins). - Supply-chain & license compliance: run
sh <plugin>/hooks/run.sh dep-license-diff <repo> [lastTag] --jsonandsh <plugin>/hooks/run.sh mcp-audit <repo> --jsonto confirm zero new strong-copyleft, unpinned, or credential issues. - Documentation & env drift: run
sh <plugin>/hooks/run.sh docs-drift <repo> --jsonandsh <plugin>/hooks/run.sh wiki-lint <wiki> --json(where applicable) so README commands, links, and.env.examplekeys match code.
If --check is set, stop here with a structured Pass/Fail readiness scorecard.
SemVer, Manifest & Changelog Synchronization
- Determine SemVer Bump:
MAJOR: breaking CLI/API/config removals or incompatible data/schema shifts without backward compatibility.MINOR: backward-compatible features, new skills/agents/commands, additive flags, or non-breaking improvements.PATCH: bug fixes, security patches, doc updates, or internal test/CI hardening.
- Inspect Changes Since Last Tag: collect
git log <lastTag>..HEAD --oneline(or diff summary) and group verified entries cleanly intoAdded,Changed,Fixed,Security, andVerification. - Sync Version Across All Declared Sources: update every manifest that declares the version (e.g.,
plugin.json,package.json,pyproject.toml, fallback version strings,README.mdheaders, and top## [X.Y.Z] - YYYY-MM-DDheading inCHANGELOG.md) atomically. - Enforce Release Hygiene: confirm zero personal home paths (
/Users/...), zero unapproved external attribution leaks, and exact schema constraints on manifests (e.g.,plugin.jsondescription length and key set).
Dry-Run Packaging & Rollout Go/No-Go Handoff
- Run dry-run artifact packaging cleanly (
npm publish --dry-run,tar/ziptarball inspection, or isolated temp-dir host bundle install + strict validation) and verify file permissions, entrypoint paths, and omitted dev/state directories (.omagy/). - Document the rollout and rollback plan (
references/rollout-and-compliance.md): canary verification commands, health/smoke probes (runtime-qa), and exact revert procedure (git revert/ deprecate version / hotfix). - Present the verified Go/No-Go scorecard, exact pending manual/confirmed release commands (tag, release notes, optional publish), and wait for explicit user authorization before executing any external publish or push.
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.

