agentleFS
MalikZuMalikZu/frappe_agents/.claude/skills/release/SKILL.md

release

Skill0 starsChanged 3 months agoMITView on GitHub

Cut a frappe_agents release — dry-run the version and notes first, dispatch release.yml, verify the tag and notes. Use whenever a release, version bump, or tag is asked for.

  • Reads credentials
  • Installs packages

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, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 183 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run it after the work is merged to main and CI is green.

    line 9
  2. Distinctive:

    BEFORE dispatching, draft the notes from the ROADMAP Done entry + PR bodies into a file (scratchpad), using exactly this template:

    line 39
  3. Very specific:

    Verify all three: the tag exists, the notes have Features/Fixes sections, and the chore(release): bumped to vX.Y.Z [skip ci] commit is on …

    line 101
  4. Distinctive:

    Never re-run the workflow for that — the tag already exists.

    line 112

“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 (semantic-release, deliberate dispatch)

Releases are never automatic: release.yml is workflow_dispatch only. Run it after the work is merged to main and CI is green.

Before dispatching

  1. Main is green (linters, server tests, harness tests on the merge commit).
  2. Dry-run locally to see the version AND the notes body before anything is public:
git clone /Users/malik/Projects/frappe_agents /tmp/rel && cd /tmp/rel
git remote set-url origin https://github.com/MalikZu/frappe_agents.git
npm install --no-save semantic-release @semantic-release/commit-analyzer \
  @semantic-release/release-notes-generator @semantic-release/exec \
  @semantic-release/git @semantic-release/github \
  conventional-changelog-conventionalcommits@8
GITHUB_TOKEN=$(gh auth token) npx semantic-release --dry-run --no-ci

Empty notes body = do not dispatch; fix first (see gotchas). feat→minor, fix/perf→patch; docs/chore/refactor/test/ci→no release.

  1. Re-stamp any skill whose "Last verified" numbers changed (dev-bench test count).

Notes are WRITTEN, not generated (house rule, 2026-08-16)

The version is computed; the notes are authored. semantic-release still decides the number and creates the tag — then the generated body gets REPLACED. Never ship the commit list as the body: commit subjects are written for reviewers at merge time, not users at upgrade time.

  1. BEFORE dispatching, draft the notes from the ROADMAP Done entry + PR bodies into a file (scratchpad), using exactly this template:

    <one sentence: what this release IS>

    New

    • <what the user can now do, where to find it — user words, one line each>

    After you upgrade <- mandatory; the section users actually need

    • <what bench migrate does to their site, in effect-words>
    • <what to enable/configure to benefit>
    • <anything that behaves differently>

    Fixed

    • <one human sentence per fix a user could have noticed>
    <details><summary>Full changelog</summary> compare link + generated list </details>

    Hard rules: no commit subjects in the body; every line user-facing; breaking changes go FIRST, bold, before New; patch releases = intro line + Fixed only; screenshots when the change is visible.

  2. Show the maintainer the draft (30-second read) before anything is public.
  3. Dry-run -> dispatch -> then IMMEDIATELY: gh release edit vX.Y.Z --notes-file <the draft>

Reference rewrite in this style: the v0.6.0 notes (see the release page after 2026-08-16, or artifact 3c382c95). Style models: esbuild (prose+examples), Biome (user-facing sentences, generated list demoted).

The v15 line releases separately

Two branches ship (see the version-branches skill): main tags vX.Y.Z, version-15 tags vX.Y.Z-v15. A -v15 tag always matches the plain release of the same number — it is the same app on the older framework, not a different version.

Two things bite here, both learned cutting v0.6.1-v15:

  • Check the number semantic-release proposes, every time. The first v15 release had no v*-v15 tag to count from, so it analysed the whole history and proposed 1.0.0. That one was cut by hand instead. Later ones can use the workflow, because the tag now exists — but read the dry run before dispatching.
  • Re-point Latest afterwards. GitHub marks the newest-published release "Latest", and the -v15 release is always published second, so it steals the badge and /releases/latest starts serving the v15 build as if it superseded the v16 one. Immediately after publishing:
gh release edit vX.Y.Z --latest      # the plain release, not the -v15 one

Dispatch and verify

gh workflow run release.yml
gh run list --workflow=release.yml -L 1   # grab the id, then: gh run watch <id>
gh release view vX.Y.Z

Verify all three: the tag exists, the notes have Features/Fixes sections, and the chore(release): bumped to vX.Y.Z [skip ci] commit is on main.

Gotchas (learned the hard way)

  • conventional-changelog-conventionalcommits must stay pinned to @8 in release.yml. Unpinned (v9+), the writer silently classifies nothing and the release body is empty — bit v0.2.0 (issue #2); its notes were hand-written.
  • .releaserc parses as YAML — renaming it to .json breaks the single-quoted prepareCmd. Plugin options must be [name, options] pairs.
  • A release that shipped with bad notes: gh release edit vX.Y.Z --notes-file f. Never re-run the workflow for that — the tag already exists.
  • A patch release must contain only fix:/perf: commits (plus release-less types like test:/docs:). One feat: makes it a minor. Check the range with git log --format='%s' <last-tag>..HEAD | sed 's/:.*//' | sort | uniq -c BEFORE the dry run, not after.

Last verified: 2026-08-16 — v0.6.1 prepared (dry run not yet dispatched).

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.