agentleFS
kapadiaskapadias/nonna/.claude/skills/release/SKILL.md

release

Skill0 starsChanged 46 days agoMITView on GitHub

Promote develop→main — human-gated production release. Creates the PR, requires explicit human approval before merge, then tags and publishes release notes.

  • 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

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 183 edited versions we read keep these.

  • 1

    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
  • could be automatic: a setting could enforce it
  1. Very specific:

    Confirm develop is green: Run /test against develop.

    line 22
  2. Distinctive:

    Stop here: Do not merge. Do not trigger a deploy.

    line 28
  3. Very specific:

    Update docs/STATUS.md with the release version and date.

    line 32
  4. Very specific:

    Run /sync to close the loop across all five mirrors.

    line 33

“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

!git branch --show-current !git status --short !git log main...develop --oneline 2>/dev/null || git log --oneline -20

Release: $ARGUMENTS

Why this is gated

Merging develop → main is a risk-increasing, outward-facing, production action — it widens blast radius to real users. Per .claude/rules/safety.md, this requires a human to approve before the merge executes. Do not merge on behalf of the user; open the PR and stop.

Steps

  1. Confirm develop is green. Run /test against develop. If anything is red, stop — do not open a release PR over a failing gate.
  2. Review the delta. The git log main...develop output above is the full promotion scope. Summarize the changes, flag anything touching auth, data, money, or irreversible actions, and confirm no secrets or debug spew are present.
  3. Open the PR develop → main. Title: release: $ARGUMENTS. Body: changelog derived from the commits above, test plan, and a prominent notice:

    HUMAN APPROVAL REQUIRED before merge. This PR promotes to production. Review the delta, confirm the gate is green, then merge manually.

  4. Stop here. Do not merge. Do not trigger a deploy. A human reviews and merges.
  5. After human merge (when instructed to continue):
    • Tag the release: git tag -a v$1 -m "Release $ARGUMENTS" on main.
    • Push the tag: git push origin v$1.
    • Update docs/STATUS.md with the release version and date.
    • Run /sync to close the loop across all five mirrors.

Output

The PR link, the delta summary, and an explicit note that merge is blocked on human approval. After merge: the tag, updated STATUS, and sync confirmation.

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.