prepare-release
Skill735 starsChanged 35 days agoMITView on GitHub
Prepare a new release of inspect_evals by creating a release branch, collecting changelog fragments, and opening a PR. Use when user asks to cut/prepare/create a new release or version bump.
- Commits and pushes
49 other projects use a version of this.
Adopted by
Most recently taken up by
- Krzysztof318/MailFathomtheir own version, first seen Nov 15, 2026
- skixmix/AntanItheir own version, first seen Nov 15, 2026
- erraggy/oastoolstheir own version, first seen Nov 15, 2026
- CherryHQ/cherry-studiotheir own version, first seen Nov 15, 2026
- leancodepl/patroltheir own version, first seen Nov 9, 2026
- Azure/azure-sdk-for-rusttheir own version, first seen Nov 8, 2026
Used with
Projects with it also use publish-release, sync-docs and 7 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.
Model Context ProtocolSkillpublish-release
Publish a GitHub release for the C# MCP SDK after a prepare-release PR has been merged. Refreshes release notes to include any PRs merged since preparation, warns about version or breaking change impacts from late-arriving PRs, and creates a draft GitHub release. Use when asked to publish a release, finalize a release, create release notes, or complete a release after the prepare-release PR has been merged.
Also in 3 projects that use this
Eipi-TongSkillsync-docs
Update SPEC.md and docs/DECISIONS.md to reflect recent code changes. Use after completing a feature, or when the user says "sync docs", "update the spec", or "log this decision".
Also in 4 projects that use this
thlaureSkillreview-change
Use this skill when the user asks for a code review, a correctness pass, a check before PR, or asks whether a Signalist change follows project conventions.
Also in 3 projects that use this
DockerSkillfix-issue
Fix a single GitHub issue end-to-end: triage, research, write the fix, review, and create a PR. Use when asked to fix an issue: "fix issue 1234", "resolve #500", "create a PR for issue 200".
Also in 4 projects that use this
kiminmonacoSkillimplement-feature
Guide for implementing features in ClaudeBar following architecture-first design, TDD, rich domain models, and Swift 6.2 patterns. Use this skill when: (1) Adding new functionality to the app (2) Creating domain models that follow user's mental model (3) Building SwiftUI views that consume domain models directly (4) User asks "how do I implement X" or "add feature Y" (5) Implementing any feature that spans Domain, Infrastructure, and App layers
Also in 3 projects that use this
SentrySkillwrite-docs
Create or update documentation pages for the Abacus docs site. Use when adding new documentation, updating existing pages, or ensuring docs stay in sync with code changes. Ensures pages follow Starlight patterns and build correctly.
Also in 3 projects that use this
Other versions49 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 49
- CherryHQ/cherry-studio★ 54ksame name
- redis/go-redis★ 22ksame name
- netbox-community/netbox★ 22ksame name
- joke2k/faker★ 19ksame name
- pybind/pybind11★ 18ksame name
- telepresenceio/telepresence★ 7.3ksame name
- modelcontextprotocol/csharp-sdk★ 4.6ksame name
- tmoroney/auto-subs★ 4.5ksame name
- CLIUtils/CLI11★ 4.5ksame name
- ethereum/consensus-specs★ 4ksame name
39 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- build-repo-contextSkill
- check-trajectories-workflowSkill
- ci-maintenance-workflowSkill
- code-quality-fix-allSkill
- code-quality-review-allSkill
- create-evalSkill
- ensure-test-coverageSkill
- eval-quality-workflowSkill
- eval-report-workflowSkill
- eval-validity-reviewSkill
- generate-asset-actionsSkill
- investigate-datasetSkill
- prepare-submission-workflowSkill
- read-eval-logsSkill
- security-audit-evalSkill
- verify-scoring-changeSkill
- write-an-adrSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 48 edited versions we read keep these.
2
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
- Very specific: line 28
If the merge fails, stop and inform the user that their local main has diverged from origin/main.
- Very specific: line 42
Ask the user what kind of bump this is, presenting the semver table from PACKAGE_VERSIONING.md:
- Distinctive: line 93
If the second pass still reports changes, resolve them before committing.
- Very specific: line 135
No manual action is required.
- Distinctive: line 140
If something goes wrong mid-workflow, the release branch can be deleted and the process restarted.
“Common” is measured: kept by at least 6 in 10 of the 48 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.
Files
Prepare a Release
This workflow prepares a new release of inspect_evals. It creates a release branch, collects changelog fragments, bumps the version tag, and opens a PR. After merge it tags the merge commit and creates a GitHub release.
Reference: PACKAGE_VERSIONING.md
Prerequisites
- The
ghCLI must be authenticated - You must have push access to the repository
- There must be changelog fragments in
changelog.d/(beyond.gitkeepandTEMPLATE.md)
Phase 1 — Prepare the release branch
Ensure
mainis up to date:git fetch origin git checkout main git merge --ff-only origin/mainIf the merge fails, stop and inform the user that their local
mainhas diverged fromorigin/main.Check for changelog fragments:
List files in
changelog.d/excluding.gitkeep,TEMPLATE.md, andREADME.*. If there are no fragments, stop and tell the user there is nothing to release.Determine the new version:
Find the current version from the latest
v*git tag:git tag --sort=-v:refname --list 'v*' | head -1Ask the user what kind of bump this is, presenting the semver table from
PACKAGE_VERSIONING.md:Component When to bump Examples Major Breaking changes Removing an eval, API changes, scorer output format changes Minor New features Adding new evals, new task parameters, new utilities Patch Bug fixes Eval fixes, scorer fixes, dataset loading fixes - Compute the new version string (e.g.
0.4.0,0.3.107). Confirm with the user.
Create the release branch:
The branch name is
release-YYYY-MM-DDusing today's date.git checkout -b release-YYYY-MM-DD
Phase 2 — Collect the changelog
Run scriv collect:
uv run scriv collect --version <NEW_VERSION>This removes the individual fragment files from
changelog.d/and prepends a new section toCHANGELOG.md.Present the changelog diff to the user for review:
git diff CHANGELOG.mdTell the user: "Please review the collected changelog above. You can edit
CHANGELOG.mddirectly — let me know when you are satisfied, or tell me what changes to make."Do not proceed until the user confirms the changelog is ready.
Normalise the collected changelog:
changelog.d/fragments are excluded from themdformatandmarkdownlint-fixpre-commit hooks (fragments are partial documents), so a hand-edit during review — or an unusual fragment — can leaveCHANGELOG.mdin a state those hooks would rewrite. That turns the Markdown Lint and README check jobs red onmainafter the release PR merges (see #2225, #2329). Run the hooks overCHANGELOG.md, then confirm a second pass is clean:uv run --group dev pre-commit run mdformat --files CHANGELOG.md || true uv run --group dev pre-commit run markdownlint-fix --files CHANGELOG.md || true # A second pass must be clean: applying fixes is fine, failing to # converge means a real error that would still break main. uv run --group dev pre-commit run mdformat --files CHANGELOG.md uv run --group dev pre-commit run markdownlint-fix --files CHANGELOG.mdIf the second pass still reports changes, resolve them before committing.
Stage and commit:
git add CHANGELOG.md changelog.d/ git commit -m "Prepare release v<NEW_VERSION>"
Phase 3 — Push and open a PR
Push the branch:
git push -u origin release-YYYY-MM-DDOpen a draft PR:
<!-- markdownlint-disable-next-line no-space-in-code -->Extract the new version's section from
CHANGELOG.md(everything from the version heading up to but not including the next##heading). Use this as the PR body:gh pr create --draft \ --title "Release v<NEW_VERSION>" \ --body "<EXTRACTED_CHANGELOG_SECTION>"Important: The PR title must start with
Release v(e.g.Release v0.4.0) — this is how therelease-on-merge.ymlworkflow identifies release PRs.Tell the user the PR URL and that it is in draft. They should mark it ready for review when appropriate.
Phase 4 — After the PR is merged (automated)
Once the release PR is merged into main, the .github/workflows/release-on-merge.yml GitHub Actions workflow automatically:
- Tags the merge commit with
v<NEW_VERSION> - Creates a GitHub release with the changelog section as the body
- Builds and publishes the package to PyPI
- Notifies Slack
No manual action is required. The package version is derived from the new tag by setuptools_scm.
Notes
- The package version is derived entirely from git tags via
setuptools_scm— there is no version file to edit. - If something goes wrong mid-workflow, the release branch can be deleted and the process restarted.
- The
vprefix on tags is required (e.g.v0.3.107, not0.3.107). - The
weekly-release.ymlworkflow can also automate Phases 1–3 on a schedule or via manual dispatch, creating the release branch and draft PR for you.
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
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.

