agentleFS
akshaypimprikarakshaypimprikar/pragma/.claude/skills/release/SKILL.md

release

Skill4 starsChanged 5 days agoMITView on GitHub

Prepare and tag a release — pre-flight checks, version bump, CHANGELOG, and tag. Invoke with a version number.

  • 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

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

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If any check fails, stop and report what must be fixed.

    line 35
  2. Very specific:

    Read .claude/context/feature-log.md if it exists — skip silently if absent (step 3 creates it if missing).

    line 39
  3. Very specific:

    Update MARKETING_VERSION and CURRENT_PROJECT_VERSION in <AppName>.xcodeproj/project.pbxproj, or project.xcproj if the project was converted …

    line 49
  4. Very specific:

    Only when there was no [Unreleased] section, use git log <last-tag>..HEAD --oneline to find what changed.

    line 67
  5. Very specific:

    Stop here: Wait for the PR to be merged before continuing.

    line 105
  6. Very specific:

    Keep the back-merge PR's head as main: check_pr_lane.py gives the release lane to a back-merge only when its head is main.

    line 122
  7. Very specific:

    Run /pipeline-review as a background task to capture any pipeline improvements surfaced during this release cycle.

    line 132

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

You are the Release Agent for an iOS app project. Your job is to prepare and tag a release.

Trigger

Invoked with a version number (e.g. /release 1.0.0).

Pre-flight checks (must all pass before continuing)

  • All tests pass on develop:
    LOG=$(mktemp -t test)
    xcodebuild test <BuildTarget> -scheme <AppName> \
      -destination 'platform=iOS Simulator,name=<simulator from AGENTS.md/CLAUDE.md>' \
      > "$LOG" 2>&1; RC=$?
    xcsift < "$LOG"
    PASSED=$(grep -E "^Test [Cc]ase '.*' passed|^[✔✓] Test .*passed" "$LOG" | grep -vc "Test run with"); FAILED=$(grep -cE "^Test [Cc]ase '.*' failed|^[✘✗] Test .*failed" "$LOG")
    [ -s "$LOG" ] && [ "$RC" -eq 0 ] && grep -q "TEST SUCCEEDED" "$LOG" && [ "$FAILED" -eq 0 ] && [ "$PASSED" -gt 0 ] \
      && echo "TESTS PASS ($PASSED tests executed)" || echo "TESTS FAIL (xcodebuild exit $RC, passed=$PASSED, failed=$FAILED)"
    Same check as /gates Gate 2: a | xcsift pipe hides xcodebuild's exit status, and a run that executes zero tests still prints TEST SUCCEEDED.
  • No TODO/FIXME in any file added since last release: git diff <last-tag>..develop -- '*.swift' | grep -E "TODO|FIXME"
  • No force-unwraps in production code added since last release (heuristic: an identifier or closing bracket followed by !, so try!/as! match and !flag/!= don't; a ! inside a string literal is a false positive, so check each hit):
    git diff <last-tag>..develop -- '<AppName>/*.swift' | grep -E '^\+.*[A-Za-z0-9_)\]]!([^=]|$)'

If any check fails, stop and report what must be fixed.

Process

Read .claude/context/feature-log.md if it exists — skip silently if absent (step 3 creates it if missing). Use it to confirm version history is consistent with the new release version before proceeding.

1. Create the release branch off develop

git checkout develop
git pull
git checkout -b release/<version>

2. Version bump

Update MARKETING_VERSION and CURRENT_PROJECT_VERSION in <AppName>.xcodeproj/project.pbxproj, or project.xcproj if the project was converted (xcodebuild -convert-project xcproj) — use whichever exists:

  • MARKETING_VERSION = <version>;
  • CURRENT_PROJECT_VERSION = <increment by 1>;

3. Update CHANGELOG.md

Rename ## [Unreleased] to the version heading, keeping its entries (add the section at the top if there is no [Unreleased]):

## [<version>] — YYYY-MM-DD

### Added
- <feature 1>
- <feature 2>

### Fixed
- <bug 1>

Only when there was no [Unreleased] section, use git log <last-tag>..HEAD --oneline to find what changed. Otherwise keep the renamed entries as they are, and do not add entries from git log on top of them.

Then create .claude/context/feature-log.md if it is absent, and append the feature-log entry to it in the same commit, so it reaches develop with the back-merge and needs no PR of its own (a separate feature-log PR made every release three PRs per repo):

## v<X.Y.Z> — YYYY-MM-DD
**Features added:** <bullet list from CHANGELOG [version] section>
**Key files changed:** <comma-separated key files or layers>
**Key architectural decisions:** <brief note or "none">

If the release branch is amended or re-cut before it merges (version or date changes, a fix folded in), update this entry in a new commit on the branch so it matches the final CHANGELOG section. An abandoned release takes its entry with the branch. A later standalone correction to feature-log.md is a docs-lane PR (it matches no app or pipeline glob), which needs only the gate summary; Gate 5 reports N/A on it.

4. Commit and push the release branch

git add <AppName>.xcodeproj/project.p* CHANGELOG.md .claude/context/feature-log.md
git commit -m "chore: bump version to <version>"
git push -u origin release/<version>

5. Verify the release branch only touches release files

The release lane (scripts/pipeline_lanes.json) exempts release/* PRs from /review and code-review on the assumption that they never carry new logic — only the mechanical version bump/CHANGELOG commit. Confirm that assumption before opening the PR:

git diff develop...HEAD --name-only

Every path in the output must be one of <AppName>.xcodeproj/project.pbxproj (or project.xcproj), CHANGELOG.md, or .claude/context/feature-log.md. If anything else appears, stop — that's unreviewed code about to bypass the review gate. Investigate before continuing. check_pr_lane.py applies the same rule in CI, so such a PR is laned by its paths and needs the full evidence.

6. Open PR to main

gh pr create \
  --title "release: v<version>" \
  --base main \
  --body "## Release v<version>
- Version bump
- CHANGELOG updated
- See git log for full changes"

Stop here. Wait for the PR to be merged before continuing. Merge it with a merge commit, not a squash: a squashed release makes the back-merge re-diff the whole release, so it would not be laned release.

7. After merge — tag and back-merge to develop

git checkout main && git pull
git tag -a v<version> -m "Release <version>"
git push origin v<version>

# develop is protected (no direct push), so the back-merge goes through a PR.
# It is laned `release` when it carries only the release commits' paths.
gh pr create --base develop --head main --title "chore: back-merge release <version> into develop" \
  --body "Back-merge of v<version> from main. Merge with a merge commit, not squash."

git branch -d release/<version>
git push origin --delete release/<version>

Keep the back-merge PR's head as main: check_pr_lane.py gives the release lane to a back-merge only when its head is main. A chore/* back-merge branch carries <AppName>.xcodeproj/project.pbxproj (or project.xcproj), so it is laned app and needs the full evidence.

8. Create GitHub release

gh release create v<version> \
  --title "v<version>" \
  --notes "$(git log <last-tag>..v<version> --oneline)"

9. Trigger pipeline review

Run /pipeline-review as a background task to capture any pipeline improvements surfaced during this release cycle. It will send a push notification when findings are ready.

Done when

PR merged to main, main tagged, back-merge PR opened to develop, GitHub release created, CHANGELOG.md committed, and /pipeline-review triggered.

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.