agentleFS
talas9talas9/anti-hall/.claude/skills/release/SKILL.md

release

Skill2 starsChanged 46 days agoMITView on GitHub

Dev-only, anti-hall repo (not part of the shipped plugin). Use when cutting an anti-hall plugin release (v*) or an engine release (ah-engine-v*) - drives RELEASING.md step by step and adds the GitHub-side steps (milestone, release-drafter draft, immutable tags, Pages, CodeQL).

  • 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

  • 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

  • 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

    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

  • parcadeiSkill

    agent-context-isolation

    Agent Context Isolation

    Also in 3 projects that use this

  • +3 more from Grinv

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    G6. Close the milestone: When every issue in it is closed or moved on:

    line 91

“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: drive RELEASING.md

RELEASING.md (repo root, read it from dev) is the authority; this skill does not repeat it. Engine binaries have their own procedure in ah-engine/RELEASING.md (on branches that carry the engine) and the ah-engine-release.yml workflow. Open (or reuse) a release issue first and track it with the gh-work skill; tick its checklist as each step lands.

git fetch origin && git show origin/dev:RELEASING.md     # read it fresh every release

Step map

StepRELEASING.mdNotes added here
0-Pick the milestone being shipped (v0.300.0, v0.301 engine-only, v1.0). gh issue list --milestone "<m>" --state open: every open item ships, moves to the next milestone with a comment, or blocks the release.
1Checklist 1 (version bump, all four manifests)node --test tests/hygiene/manifest-drift.test.js proves they agree.
2Checklist 2 (CHANGELOG)Compare with the release-drafter draft (G1) so no merged PR is missing.
3Checklist 3 + "Doc-currency rule"Sweep every doc, both ports (Claude + Codex).
4Checklist 4 (verify)Full node --test + doctor, this change, this session.
5Checklist 5 (commit + push dev)Repo git identity; no AI-credit lines.
6Checklist 6 (optional rc-v* full matrix)Needed when the change touches CI, hooks across OSes, or the engine bootstrap.
7Checklist 7 (PR dev -> main)Merge commit only (G2). Merging IS the release.
8Checklist 8 (tag + GitHub Release)Tags are immutable (G3); publish the drafter draft (G1).
9Checklist 9 (marketplace propagate)Never overwrite version-pinned cache snapshots.
10Checklist 10 + "Publish venues"Notable releases only.
11-Post-merge GitHub checks (G4, G5) and milestone close (G6).

GitHub-side steps

G1. Release-drafter draft. release-drafter.yml keeps one DRAFT release up to date from PRs merged into main, grouped by type:* labels; it never publishes or tags. Before tagging:

gh release list -R talas9/anti-hall --limit 5          # the draft shows as "Draft"
gh release view <draft-tag> -R talas9/anti-hall        # check PR list, categories, resolved version

Its resolved version must equal the bumped version; if not, the semver bump or a PR's type:* label is wrong: fix the label, not the draft. Replace the draft body with the CHANGELOG section (CHANGELOG is the authority), then publish it on the new tag:

gh release edit <draft-tag> -R talas9/anti-hall --tag v<version> --title v<version> \
  --notes-file <changelog-section.md> --draft=false --latest

(or gh release create v<version> --notes-file ... when no draft exists).

G2. Release PR. gh pr create --base main --head dev; required checks dev-only and tests-passed; gh pr merge <pr> --merge. Never squash, never merge red.

G3. Tags are immutable. The "release tags are immutable" ruleset covers refs/tags/v* and refs/tags/ah-engine-v*: no update, no delete, no force. A wrong tag cannot be fixed; ship the next patch version instead. So tag only after the main merge is green and pulled:

git fetch origin && git switch --detach origin/main && git log -1 --oneline   # the merge commit
git tag v<version> && git push origin v<version>

Engine: ah-engine-v<X.Y.Z> is pushed only after the lock PR from the prepare run is merged (the tag triggers publish, which fails without a matching prepare). rc-v* tags are not covered by the ruleset and are left in place (owner prunes).

G4. Docs site (Pages). pages.yml builds tools/build-site.js and deploys on every push to main, so the release merge updates the site. Check it:

gh run list -R talas9/anti-hall --workflow pages.yml --branch main --limit 1
gh api repos/talas9/anti-hall/pages --jq .html_url     # 404 = Pages not enabled yet: see RELEASING.md step 7

G5. CodeQL. The repo uses CodeQL default setup (Settings -> Code security); the codeql.yml advanced workflow is manual-only and must stay so while default setup is on (both cannot run). After the merge:

gh api repos/talas9/anti-hall/code-scanning/default-setup --jq '{state,languages}'
gh api 'repos/talas9/anti-hall/code-scanning/alerts?state=open&ref=refs/heads/main' --jq length

New open alerts on main get an issue (type:bug, area:ci or the code's area) before the release is called done.

G6. Close the milestone. When every issue in it is closed or moved on:

gh api 'repos/talas9/anti-hall/milestones?state=open' --jq '.[]|"\(.number) \(.title) \(.open_issues)"'
gh api -X PATCH repos/talas9/anti-hall/milestones/<number> -f state=closed

Then comment the release link and the verification evidence on the release issue and close it through its PR or gh issue close <n> --comment "<evidence>".

Done means

main merge green (tests-passed, dev-only), tag pushed, GitHub Release published from the CHANGELOG section, Pages run green, CodeQL clean or ticketed, milestone closed, marketplace dir propagated. Anything missing stays an open checklist item on the release issue.

Model routing for agents and lanes: see the "Model routing" section in .claude/skills/README.md.

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.