release
Skill8 starsChanged 8 months agoMITView on GitHub
Use when the user wants to release a new version, says "time to release", "let's release", "cut a release", "version bump", or similar. Orchestrates the full release workflow including milestone check, version bump, changelog generation, validation, tagging, and PR creation. Also invocable as /release.
- Commits and pushes
193 other projects use a version of this.
Adopted by
Most recently taken up by
- naomiaro/waveform-playlisttheir own version, first seen Nov 16, 2026
- osmlab/name-suggestion-indextheir own version, first seen Nov 16, 2026
- vulnerability-lookup/vulnerability-lookuptheir own version, first seen Nov 16, 2026
- ClickHouse/mcp-clickhousetheir own version, first seen Nov 16, 2026
- bpatrik/pigallery2their own version, first seen Nov 16, 2026
- Shasnow/StarRailAssistanttheir own version, first seen Nov 16, 2026
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.
MicrosoftSkillcreate-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
GrinvSkillchangelog-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 AzureSkillcomponent-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
GrinvSkilldocs-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 AzureSkilldocumentation-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
parcadeiSkillagent-context-isolation
Agent Context Isolation
Also in 3 projects that use this
- +3 more from Grinv
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- paperclipai/paperclip★ 114ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 73ksame name
- traefik/traefik★ 66ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 64ksame name
- AmruthPillai/Reactive-Resume★ 46ksame name
- amruthpillai/reactive-resume★ 46ksame name
- reactive-resume/reactive-resume★ 46ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
183 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 repository5 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- api-designSkill
- applescript-omnifocusSkill
- integration-testingSkill
- performance-patternsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. 0 are common, 14 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
14
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Before creating a release branch, verify the milestone is ready.
- Distinctive: line 19
If there are multiple open milestones, ask the user which one to release.
- Distinctive: line 21
If the target milestone has open issues, stop and ask the user:
- Distinctive: line 27
Do NOT proceed until all issues in the target milestone are closed or moved.
- Very specific: line 33
Read the current version from pyproject.toml (authoritative source).
- Distinctive: line 37
Wait for confirmation before proceeding.
- Very specific: line 49
Update version in ALL of these files (pyproject.toml is authoritative):
- Distinctive: line 54
README.md: - All references to the old version (check with grep for old version string)
- Distinctive: line 56
Use the Edit tool for each file.
- Very specific: line 64
Use the previous version tag directly (e.g., v0.8.1).
- Very specific: line 73
Use Keep a Changelog format: ## [X.Y.Z] - YYYY-MM-DD
- Distinctive: line 116
If Critical issues are found, stop and fix before proceeding.
- Distinctive: line 130
Verify accuracy against changes in this release:
- Distinctive: line 135
Test count / coverage stats in CLAUDE.md header
- Distinctive: line 142
Run ALL validation checks.
- Distinctive: line 174
If any check fails, fix the issue and re-run.
- Distinctive: line 199
After the user approves the PR:
- Distinctive: line 229
After the tag is pushed, close the milestone:
- Very specific: line 239
Use rebase merge for release PRs.
“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.
Files
Release Workflow
This skill orchestrates a complete release. Follow each phase in order. Stop and report if any phase fails.
Phase 1: Milestone Check
Before creating a release branch, verify the milestone is ready.
- Determine the target milestone. Look at open milestones:
gh api "repos/{owner}/{repo}/milestones?state=open&sort=due_on" --jq '.[] | "\(.number) \(.title) open:\(.open_issues) closed:\(.closed_issues)"' - If there are multiple open milestones, ask the user which one to release.
- If the target milestone has open issues, stop and ask the user:
- List the open issues:
gh api "repos/{owner}/{repo}/milestones/{number}/issues?state=open" --jq ...(or usegh issue list --milestone) - Present options: a. Move open issues to the next milestone (specify or create it) b. Pause to work on the open issues first c. Close the issues if they're no longer relevant
- Do NOT proceed until all issues in the target milestone are closed or moved.
- List the open issues:
- Once the milestone is clean (0 open issues), proceed.
Phase 2: Version Number
- Read the current version from
pyproject.toml(authoritative source). - The milestone title tells you the target version (e.g.,
v0.7.3means version0.7.3). - Validate it's a valid semver bump from the current version.
- Present the version to the user for confirmation: "Release version X.Y.Z? (current: A.B.C)"
- Wait for confirmation before proceeding.
Phase 3: Create Release Branch
git checkout main
git pull origin main
git checkout -b release/vX.Y.ZPhase 4: Bump Version
Update version in ALL of these files (pyproject.toml is authoritative):
- pyproject.toml -
version = "X.Y.Z" - src/omnifocus_mcp/init.py -
__version__ = "X.Y.Z" - CLAUDE.md (.claude/CLAUDE.md) -
**Version:** vX.Y.Zin the header line - README.md - All references to the old version (check with grep for old version string)
Use the Edit tool for each file. Be precise about what to change.
Phase 5: Generate CHANGELOG
- Get all commits since the last release:
Use the previous version tag directly (e.g.,git log v{previous_version}..HEAD --onelinev0.8.1). Do NOT usegit describe --tags --abbrev=0— it walks commit ancestry and may not find tags that were created before a squash/rebase merge. - Get merged PRs since the last release:
(Use the date of the last tag)gh pr list --state merged --base main --search "merged:>YYYY-MM-DD" --json number,title,labels - Generate a CHANGELOG entry following the existing format in CHANGELOG.md:
- Use Keep a Changelog format:
## [X.Y.Z] - YYYY-MM-DD - Categorize changes: Added, Changed, Fixed, Removed
- Reference PR/issue numbers with (#N)
- Be concise but descriptive
- Include today's date
- Use Keep a Changelog format:
- Insert the new entry at the top of CHANGELOG.md (after the header, before the previous version).
Phase 6: Test Coverage Review
- Run coverage report:
pytest --cov=omnifocus_mcp --cov-report=term-missing tests/ -q - Compare overall coverage against the
fail_underthreshold inpyproject.toml. If coverage dropped below the threshold, stop and report — new code likely needs tests. - Get the cumulative diff to identify changed files:
git diff v{previous}..HEAD --stat - Audit changed
src/files for adequate test coverage:- New code paths without unit tests
- Modified AppleScript strings without integration tests (per CLAUDE.md hard rule: "If you wrote or modified an AppleScript string, integration tests must cover it before merge")
- New parameters or return fields without test assertions
- Flag any gaps. If coverage dropped or critical paths are untested, stop and fix before proceeding.
Phase 7: Code Review
- Get the cumulative diff since the last release:
git diff v{previous}..HEAD - Launch the
superpowers:code-revieweragent to review the full diff. Provide context about the release scope (PRs included, features added/changed). - The reviewer will report issues by severity:
- Critical — security issues, data loss risks, correctness bugs → blocks the release
- Important — code quality, missed edge cases → fix or document in PR
- Minor — style, naming, suggestions → note in PR description
- If Critical issues are found, stop and fix before proceeding.
- Include Important/Minor findings in the release PR description under a "Code Review Notes" section.
Phase 8: Documentation Review
- Enumerate documentation to check:
README.md— feature descriptions, installation, usage examples.claude/CLAUDE.md— version, test counts, coverage %, API surface count, performance baselinesCHANGELOG.md— new entry completenessdocs/**— architecture, profiling, AppleScript gotchas, automation notes- Tool docstrings in
src/omnifocus_mcp/server_fastmcp.py - Skill files in
.claude/skills/
- Verify accuracy against changes in this release:
- Stale version numbers (should still be old version — Phase 4 bumped them)
- Outdated performance baselines if perf-related changes were made
- Missing feature documentation for new capabilities
- Incorrect cross-references between docs
- Test count / coverage stats in CLAUDE.md header
- README coverage badge (
coverage-XX%25-brightgreen) matches actual coverage
- Flag discrepancies and fix them on the release branch before proceeding.
Phase 9: Validation
Run ALL validation checks. Stop on any failure.
- Version sync check:
./scripts/check_version_sync.sh - Client-server parity:
./scripts/check_client_server_parity.sh - Complexity check:
./scripts/check_complexity.sh - Unit tests:
make test - Dependency audit:
./scripts/check_dependencies.sh - AppleScript safety audit:
./scripts/check_applescript_safety.sh
If any check fails, fix the issue and re-run. Do not proceed with failures.
Phase 10: Commit, Push, and PR
- Commit the version bump and changelog:
git add -A git commit -m "release: vX.Y.Z" - Push the branch:
git push -u origin release/vX.Y.Z - Create the PR to main:
Include any Code Review Notes from Phase 7 in the PR body.gh pr create --title "release: vX.Y.Z" --body "..." - Tell the user the PR is ready for review. Do NOT merge it automatically.
Phase 11: Merge, Tag, and Push Tag
After the user approves the PR:
- Merge using rebase merge:
gh pr merge NNN --rebase --delete-branch - Switch to main and pull:
git checkout main git pull origin main - Create the tag on main (where it will be reachable via
git describe):./scripts/create_tag.sh vX.Y.Z - Push the tag:
git push origin vX.Y.Z - Verify tag reachability:
git describe --tags --abbrev=0 # Should return vX.Y.Z
Phase 12: Close Milestone
After the tag is pushed, close the milestone:
gh api -X PATCH "repos/{owner}/{repo}/milestones/{number}" -f state=closedNotes
- CHANGELOG is only updated on release branches, never on feature branches.
- Tags are created on main after the PR merge. This ensures they are reachable via
git describe, which walks commit ancestry. Squash/rebase merges create new commits, so tags on the release branch would become orphaned. - Use rebase merge for release PRs. Merge commits are blocked by
required_linear_historyon main. - Integration tests (
make test-integration,make test-e2e) require a real OmniFocus test database. Ask the user if they want to run them — they're optional for the release validation.
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.

