release-publish
Skill7 starsChanged 5 months agoMITView on GitHub
Publish a prepared release — push the release branch, open an auto-merge PR, monitor merge, push the tag to trigger CI, and clean up. Use when asked to "发布", "publish release", "release publish", "push release", or after `/release-version` has prepared the branch.
- Commits and pushes
9 other projects use a version of this.
Adopted by
Most recently taken up by
- skforecast/skforecasttheir own version, first seen Nov 16, 2026
- Alex5350/arsenaltheir own version, first seen Nov 1, 2026
- Shri-Phnx/claude-skillstheir own version, first seen Oct 13, 2026
- bkywksj/knowledge-basetheir own version, first seen Oct 8, 2026
- clawwork-ai/ClawWorktheir own version, first seen Oct 8, 2026
- mono/SkiaSharptheir own version, first seen Oct 8, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- mono/SkiaSharp★ 5.6ksame name
- skforecast/skforecast★ 1.5ksame name
- chrysb/alphaclaw★ 1.5ksame name
- clawwork-ai/ClawWork★ 533same name
- bkywksj/knowledge-base★ 346same name
- Shri-Phnx/claude-skills★ 2same name
- Alex5350/arsenal★ 0same name
- KcAnom/pi-fairy-tales-chains★ 0same name
- metyatech/skill-release-publish★ 0same name
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 repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- release-tagSkill
- release-versionSkill
- self-checkSkill
- submit-prSkill
- sync-agent-skillsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. 0 are common, 12 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
12
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 12
After /release-version has created the release branch with version bump and release notes
- Distinctive: line 13
When asked to "publish", "发布", or "push the release"
- Distinctive: line 14
When the release branch is ready and needs to go through the PR flow
- Very specific: line 16
Do not use for version bumping or release notes — that is /release-version.
- Distinctive: line 38
If not on a release branch, check out the correct one:
- Distinctive: line 50
Verify the branch has at least the version bump commit:
- Distinctive: line 68
Create a PR targeting main with auto-merge enabled:
- Distinctive: line 87
Do not use a heredoc with single-quoted delimiter — write the body as a plain string with the version substituted directly.
- Very specific: line 96
If gh pr merge --auto fails (e.g.
- Distinctive: line 121
If the PR is merged:
- Distinctive: line 137
If the PR is not merged after 10 minutes, tell the user:
- Distinctive: line 151
Wait 2 minutes for CI to start, then check the release workflow status:
- Distinctive: line 157
If the workflow is still running, tell the user:
- Distinctive: line 162
If the workflow completed successfully, confirm:
- Distinctive: line 192
CI fails on push: check Actions logs, fix on the release branch, re-push
“Common” is measured: kept by at least 6 in 10 of the 8 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 Publish
Takes a prepared release branch (from /release-version) and drives it through PR creation, merge, tag push, and CI trigger.
When to Use
- After
/release-versionhas created the release branch with version bump and release notes - When asked to "publish", "发布", or "push the release"
- When the release branch is ready and needs to go through the PR flow
Do not use for version bumping or release notes — that is /release-version.
Prerequisites
- A
chore/release-v{X.Y.Z}branch exists with committed version bump and release notes ghCLI authenticated with push/PR access- Clean working tree
Workflow
Execute these phases in order. Report the output of each phase before moving on.
Phase 1 — Validate Release Branch
Confirm the current branch is the release branch:
git branch --show-currentIf not on a release branch, check out the correct one:
git checkout chore/release-v{NEXT_VERSION}Extract the version from the branch name or
package.json:VERSION=$(node -p "require('./package.json').version")Verify the branch has at least the version bump commit:
git log main..HEAD --oneline
Output: confirmed release branch and version string.
Phase 2 — Push and Create Auto-Merge PR
Push the release branch:
git push -u origin chore/release-v{NEXT_VERSION}Create a PR targeting
mainwith auto-merge enabled:gh pr create \ --base main \ --head chore/release-v{NEXT_VERSION} \ --title "chore(release): v{VERSION}" \ --body "## Release v{VERSION} Bumps version to v{VERSION} and adds release notes. ### Changes - Version bump in package.json, tauri.conf.json, Cargo.toml - Release notes at docs/releases/v{VERSION}.md " gh pr merge --auto --squashDo not use a heredoc with single-quoted delimiter — write the body as a plain string with the version substituted directly.
Capture the PR info:
PR_URL=$(gh pr view --json url -q .url) PR_NUMBER=$(gh pr view --json number -q .number)- If
gh pr merge --autofails (e.g. branch protection requires reviews, or auto-merge is not enabled on the repo), report the PR URL to the user and tell them to review and merge manually. Then skip to Phase 4.
Output: PR_NUMBER, PR_URL, auto-merge status.
Phase 3 — Monitor Merge and Push Tag
Switch back to
main:git checkout mainPoll the PR status until it merges or a timeout is reached. Check every 15 seconds, up to 40 attempts (10 minutes total):
gh pr view "$PR_NUMBER" --json state,mergedAt -q '.state'Possible states:
MERGED— proceed to publishCLOSED— PR was closed without merging; tell the userOPEN— still waiting; continue polling
If the PR is merged:
a. Pull the latest
main:git pull origin mainb. Verify the version in
package.jsonmatchesv{VERSION}.c. Create and push the release tag to trigger CI:
pnpm release:tag v{VERSION}If the PR is not merged after 10 minutes, tell the user:
The release PR has not been merged yet. Please review and merge it manually.
After merging, run
pnpm release:tag v{VERSION}onmainto publish.Then end the workflow.
Output: tag pushed and CI triggered, OR instructions for manual merge.
Phase 4 — Post-Release
Wait 2 minutes for CI to start, then check the release workflow status:
gh run list --workflow=release.yml --limit=1 --json status,conclusion,databaseIdIf the workflow is still running, tell the user:
Release build is in progress. Check the assets at: https://github.com/hhhyyyy99/prot-skills/releases
If the workflow completed successfully, confirm:
Release v{VERSION} is complete. Download assets are available on the GitHub release page.
Clean up the local release branch:
git branch -d chore/release-v{VERSION} git push origin --delete chore/release-v{VERSION}
Output: release confirmed and cleanup done.
Quick Reference
| Step | Command |
| Create PR | gh pr create --base main --head <branch> |
| Enable auto-merge | gh pr merge --auto --squash |
| Check PR status | gh pr view <N> --json state,mergedAt |
| Create tag | pnpm release:tag v{VERSION} |
| Watch CI | gh run list --workflow=release.yml --limit=1 |
Error Handling
- Tag already exists locally:
git tag -d v{VERSION}then retry - Tag exists remotely but not locally:
git fetch origin tag v{VERSION} - CI fails on push: check Actions logs, fix on the release branch, re-push
- Auto-merge unavailable: report PR URL, ask user to merge manually, end workflow
- PR already exists: find the existing PR with
gh pr list --head chore/release-v{VERSION}and report its URL
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.

