agentleFS
YomudoglyYomudogly/oh-my-agy/skills/release/SKILL.md

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

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

    create-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

  • GrinvSkill

    changelog-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

  • GrinvSkill

    docs-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 AzureSkill

    component-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 AzureSkill

    documentation-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-devSkill

    launch-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

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
  1. Very specific:

    Confirmation gate for irreversible actions: never execute git tag, git push, GitHub release creation, or a live npm publish without …

    line 21
  2. Very specific:

    Zero unverified greenwashing: never bump version manifests or CHANGELOG.md until tests, license checks, doc parity, and floor guards pass …

    line 22
  3. Very specific:

    No fabricated release metrics or unverified diffs: every item in CHANGELOG.md must come from observed commits, diffs, or verified artifact …

    line 23
  4. Very specific:

    Run read-only readiness checks in order (delegate to devops-engineer, doc-steward, or supply-chain-auditor for parallel audit/fixes):

    line 27
  5. Very specific:

    Git hygiene & clean diff: verify working tree expectations (git status --short), ensure zero untracked temp debris, and run sh …

    line 29
  6. Very specific:

    Test, lint, syntax & host parity suite: run full repo tests, POSIX sh -n syntax checks on launchers, CI build scripts, and host validation …

    line 30
  7. Very specific:

    Supply-chain & license compliance: run sh <plugin>/hooks/run.sh dep-license-diff <repo> [lastTag] --json and sh <plugin>/hooks/run.sh …

    line 31
  8. Very specific:

    Documentation & env drift: run sh <plugin>/hooks/run.sh docs-drift <repo> --json and sh <plugin>/hooks/run.sh wiki-lint <wiki> --json …

    line 32
  9. Very specific:

    If --check is set, stop here with a structured Pass/Fail readiness scorecard.

    line 34
  10. Very specific:

    Sync Version Across All Declared Sources: update every manifest that declares the version (e.g., plugin.json, package.json, pyproject.toml, …

    line 43
  11. Very specific:

    Run dry-run artifact packaging cleanly (npm publish --dry-run, tar/zip tarball inspection, or isolated temp-dir host bundle install + …

    line 48
  12. Very specific:

    Document the rollout and rollback plan (references/rollout-and-compliance.md): canary verification commands, health/smoke probes …

    line 49

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 live npm publish without explicit user approval in the active turn (avoid running live npm publish cleanly by validating --dry-run first).
  • Zero unverified greenwashing: never bump version manifests or CHANGELOG.md until tests, license checks, doc parity, and floor guards pass cleanly.
  • No fabricated release metrics or unverified diffs: every item in CHANGELOG.md must 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):

  1. Git hygiene & clean diff: verify working tree expectations (git status --short), ensure zero untracked temp debris, and run sh <plugin>/hooks/run.sh floor-guard <repo> --json (total: 0, zero secrets, disabled tests, or unresolved blockers).
  2. Test, lint, syntax & host parity suite: run full repo tests, POSIX sh -n syntax checks on launchers, CI build scripts, and host validation (skill-validate --strict, host-validate --strict when shipping plugins).
  3. Supply-chain & license compliance: run sh <plugin>/hooks/run.sh dep-license-diff <repo> [lastTag] --json and sh <plugin>/hooks/run.sh mcp-audit <repo> --json to confirm zero new strong-copyleft, unpinned, or credential issues.
  4. Documentation & env drift: run sh <plugin>/hooks/run.sh docs-drift <repo> --json and sh <plugin>/hooks/run.sh wiki-lint <wiki> --json (where applicable) so README commands, links, and .env.example keys match code.

If --check is set, stop here with a structured Pass/Fail readiness scorecard.

SemVer, Manifest & Changelog Synchronization

  1. 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.
  2. Inspect Changes Since Last Tag: collect git log <lastTag>..HEAD --oneline (or diff summary) and group verified entries cleanly into Added, Changed, Fixed, Security, and Verification.
  3. 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.md headers, and top ## [X.Y.Z] - YYYY-MM-DD heading in CHANGELOG.md) atomically.
  4. Enforce Release Hygiene: confirm zero personal home paths (/Users/...), zero unapproved external attribution leaks, and exact schema constraints on manifests (e.g., plugin.json description length and key set).

Dry-Run Packaging & Rollout Go/No-Go Handoff

  1. Run dry-run artifact packaging cleanly (npm publish --dry-run, tar/zip tarball inspection, or isolated temp-dir host bundle install + strict validation) and verify file permissions, entrypoint paths, and omitted dev/state directories (.omagy/).
  2. 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).
  3. 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.

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.