release-tag
Skill7 starsChanged 5 months agoMITView on GitHub
Direct release from main — bump version, verify, push commit, create tag to trigger CI. Use when asked to "tag release", "直接发版", "push tag", "release on main", or when the release branch has already been merged and only the tag push remains.
- Commits and pushes
4 other projects use a version of this.
Adopted by
Most recently taken up by
- poweruserz/OpenTokenUsagetheir own version, first seen Oct 15, 2026
- TGPSKI/leathertheir own version, first seen Sep 7, 2026
- KcAnom/pi-fairy-tales-chainstheir own version, first seen Jul 17, 2026
- KhaledSaeed18/dotclaudetheir own version, first seen Jul 4, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- poweruserz/OpenTokenUsage★ 52same name
- TGPSKI/leather★ 17same name
- KhaledSaeed18/dotclaude★ 5same name
- KcAnom/pi-fairy-tales-chains★ 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-publishSkill
- 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
14 rules. 0 are common, 9 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
9
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 13
After a release branch has been merged and only the tag push remains
- Distinctive: line 14
When the user says "直接发版" or "push a tag"
- Distinctive: line 15
When auto-merge PR is not available and the user prefers a direct push
- Very specific: line 17
Do not use for PR-based releases — that is /release-publish.
- Distinctive: line 39
If there are uncommitted changes, stop and tell the user to commit or stash first.
- Very specific: line 41
Read the current version from package.json and ask the user which bump level to use:
- Very specific: line 60
Verify the version is correct in package.json.
- Distinctive: line 68
Run a local build check:
- Very specific: line 74
If cargo test is available:
- Distinctive: line 92
Create and push the release tag:
- Distinctive: line 106
Wait 2 minutes for CI to start, then check the release workflow:
- Distinctive: line 122
After CI succeeds, open the draft release and verify assets before publishing it.
- Very specific: line 150
pnpm release:versionfails: ensure cargo is available and src-tauri/Cargo.toml is valid - Distinctive: line 151
CI fails: check Actions logs, fix on main, re-push and re-tag
“Common” is measured: kept by at least 6 in 10 of the 4 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 Tag
Direct-to-main release flow. Bumps the version, verifies locally, pushes the commit, and creates the release tag to trigger CI. Skips the PR step — use /release-publish for the PR-based flow.
When to Use
- Releasing directly from
mainwithout a PR - After a release branch has been merged and only the tag push remains
- When the user says "直接发版" or "push a tag"
- When auto-merge PR is not available and the user prefers a direct push
Do not use for PR-based releases — that is /release-publish.
Prerequisites
- On
mainbranch with no uncommitted changes pnpmandcargoavailable- Push access to
origin/main
Workflow
Phase 1 — Prepare Main
Confirm on
mainand up to date:git checkout main git pull origin main git status --shortIf there are uncommitted changes, stop and tell the user to commit or stash first.
- Read the current version from
package.jsonand ask the user which bump level to use:patch— bug fixes, CI fixes (e.g. 0.0.4 → 0.0.5)minor— new features, backward compatible (e.g. 0.0.4 → 0.1.0)major— breaking changes (e.g. 0.0.4 → 1.0.0)
Output: confirmed bump level.
Phase 2 — Bump Version
Bump the version:
pnpm release:version {LEVEL}This updates
package.json,src-tauri/tauri.conf.json,src-tauri/Cargo.toml,src-tauri/Cargo.lockand commitschore(release): bump version to {NEXT_VERSION}.- Verify the version is correct in
package.json.
Output: version bump committed on main.
Phase 3 — Verify
Run a local build check:
pnpm buildIf
cargo testis available:cd src-tauri && cargo test
Output: build and tests pass.
Phase 4 — Push and Tag
Push the version bump commit to
main:git push origin mainCreate and push the release tag:
pnpm release:tag v{NEXT_VERSION}This creates an annotated tag and pushes it to
origin, which triggers.github/workflows/release.yml.
Output: tag pushed, CI triggered.
Phase 5 — Monitor Release
Wait 2 minutes for CI to start, then check the release workflow:
gh run list --workflow=release.yml --limit=1 --json status,conclusion,databaseIdIf running:
Release build is in progress. Check assets at: https://github.com/hhhyyyy99/prot-skills/releases
If completed successfully:
Release v{NEXT_VERSION} is complete. Download assets are available on the GitHub release page.
- After CI succeeds, open the draft release and verify assets before publishing it.
Output: release confirmed or CI status reported.
Quick Reference
| Step | Command |
| Bump version | pnpm release:version patch|minor|major |
| Create tag | pnpm release:tag v{VERSION} |
| Watch CI | gh run list --workflow=release.yml --limit=1 |
Pre-Release Checklist
mainis up to date- Working tree is clean
- Version bump committed
pnpm buildpassescargo testpasses- Tag matches the new version
- Tag is pushed to
origin
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} pnpm release:versionfails: ensurecargois available andsrc-tauri/Cargo.tomlis valid- CI fails: check Actions logs, fix on
main, re-push and re-tag - Windows release fails in
pnpm app:check: known CRLF issue inCargo.tomlortauri.conf.json, runpnpm test scripts/sync-app-metadata.test.mjsto verify
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.

