agentleFS
hhhyyyy99hhhyyyy99/prot-skills/.agents/skills/release-tag/SKILL.md

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

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. poweruserz/OpenTokenUsage★ 52same name
    2. TGPSKI/leather★ 17same name
    3. KhaledSaeed18/dotclaude★ 5same name
    4. 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.

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
  1. Distinctive:

    After a release branch has been merged and only the tag push remains

    line 13
  2. Distinctive:

    When the user says "直接发版" or "push a tag"

    line 14
  3. Distinctive:

    When auto-merge PR is not available and the user prefers a direct push

    line 15
  4. Very specific:

    Do not use for PR-based releases — that is /release-publish.

    line 17
  5. Distinctive:

    If there are uncommitted changes, stop and tell the user to commit or stash first.

    line 39
  6. Very specific:

    Read the current version from package.json and ask the user which bump level to use:

    line 41
  7. Very specific:

    Verify the version is correct in package.json.

    line 60
  8. Distinctive:

    Run a local build check:

    line 68
  9. Very specific:

    If cargo test is available:

    line 74
  10. Distinctive:

    Create and push the release tag:

    line 92
  11. Distinctive:

    Wait 2 minutes for CI to start, then check the release workflow:

    line 106
  12. Distinctive:

    After CI succeeds, open the draft release and verify assets before publishing it.

    line 122
  13. Very specific:

    pnpm release:version fails: ensure cargo is available and src-tauri/Cargo.toml is valid

    line 150
  14. Distinctive:

    CI fails: check Actions logs, fix on main, re-push and re-tag

    line 151

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 main without 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 main branch with no uncommitted changes
  • pnpm and cargo available
  • Push access to origin/main

Workflow


Phase 1 — Prepare Main

  1. Confirm on main and up to date:

    git checkout main
    git pull origin main
    git status --short

    If there are uncommitted changes, stop and tell the user to commit or stash first.

  2. Read the current version from package.json and 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

  1. Bump the version:

    pnpm release:version {LEVEL}

    This updates package.json, src-tauri/tauri.conf.json, src-tauri/Cargo.toml, src-tauri/Cargo.lock and commits chore(release): bump version to {NEXT_VERSION}.

  2. Verify the version is correct in package.json.

Output: version bump committed on main.


Phase 3 — Verify

  1. Run a local build check:

    pnpm build
  2. If cargo test is available:

    cd src-tauri && cargo test

Output: build and tests pass.


Phase 4 — Push and Tag

  1. Push the version bump commit to main:

    git push origin main
  2. Create 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

  1. Wait 2 minutes for CI to start, then check the release workflow:

    gh run list --workflow=release.yml --limit=1 --json status,conclusion,databaseId
  2. If running:

    Release build is in progress. Check assets at: https://github.com/hhhyyyy99/prot-skills/releases

  3. If completed successfully:

    Release v{NEXT_VERSION} is complete. Download assets are available on the GitHub release page.

  4. After CI succeeds, open the draft release and verify assets before publishing it.

Output: release confirmed or CI status reported.


Quick Reference

StepCommand
Bump versionpnpm release:version patch|minor|major
Create tagpnpm release:tag v{VERSION}
Watch CIgh run list --workflow=release.yml --limit=1

Pre-Release Checklist

  • main is up to date
  • Working tree is clean
  • Version bump committed
  • pnpm build passes
  • cargo test passes
  • 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:version fails: ensure cargo is available and src-tauri/Cargo.toml is valid
  • CI fails: check Actions logs, fix on main, re-push and re-tag
  • Windows release fails in pnpm app:check: known CRLF issue in Cargo.toml or tauri.conf.json, run pnpm test scripts/sync-app-metadata.test.mjs to verify

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.