agentleFS
skixmixskixmix/AntanI/.claude/skills/prepare-release/SKILL.md

prepare-release

Skill2 starsChanged 10 days agoMITView on GitHub

Prepare an AntanI release PR. Bumps the version in tauri.conf.json, Cargo.toml, and package.json in sync, branches from main, commits, pushes, and opens a PR titled "Release vX.Y.Z" via gh. Use when the user asks to prepare/cut/ship a release, or says something like "prepare the release PR" or "release vX.Y.Z".

  • Commits and pushes

49 other projects use a version of this.

Adopted by

Most recently taken up by

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 ProtocolSkill

    publish-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 4 projects that use this

  • MichaelRyanWoodSkill

    sync-docs

    Audit and update AI support documentation (ARCHITECTURE.md, SECURITY.md, CLAUDE.md, diagrams/) to reflect recent code changes. Run after completing a feature, fix, or refactor to keep docs accurate.

    Also in 4 projects that use this

  • thlaureSkill

    review-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

  • DockerSkill

    fix-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

  • kiminmonacoSkill

    implement-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

  • SentrySkill

    write-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

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is 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.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Current version: read .version from src-tauri/tauri.conf.json — this is the single source of truth for "current version."

    line 21
  2. Distinctive:

    Target version: if the user gave an explicit version (e.g.

    line 24
  3. Distinctive:

    Write a 1–2 sentence plain-English summary of what the change actually does from a user's perspective — not a restatement of the commit …

    line 56

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

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

Prepare an AntanI release

Merging a PR titled Release vX.Y.Z into main is what triggers .github/workflows/release.yml (build + draft GitHub Release), which in turn triggers .github/workflows/bump-tap.yml on publish (updates the skixmix/homebrew-antani tap). This skill only prepares and opens that PR — it never merges, publishes a release, or touches the tap directly.

Steps

  1. Preconditions: gh auth status must succeed (if not, tell the user to run gh auth login themselves — never attempt to log them in). Working tree must be clean; if not, stop and ask rather than stashing/discarding. Checkout and pull main.
  2. Current version: read .version from src-tauri/tauri.conf.json — this is the single source of truth for "current version."
  3. Target version: if the user gave an explicit version (e.g. "release v0.2.0"), use it. Otherwise inspect commits since the last vX.Y.Z tag (git log <last-tag>..main --oneline) and suggest a bump using conventional-commit-ish signal: a ! after the type or a BREAKING CHANGE footer -> major; any feat: -> minor; otherwise -> patch. Always confirm the suggested version with the user via AskUserQuestion before proceeding — never assume.
  4. Bump in sync, exact same version string in all three:

    • src-tauri/tauri.conf.json ("version" field)
    • src-tauri/Cargo.toml (version = "..." under [package]; BSD sed has no 0,/re/ address, so edit that line explicitly)
    • package.json ("version" field)

    Then refresh src-tauri/Cargo.lock so its antani entry matches (cargo update -p antani --offline in src-tauri). A lagging lockfile breaks any --locked build.

  5. Branch: git checkout -b release/vX.Y.Z from main.
  6. Commit: git commit -am "Release vX.Y.Z" — only the three version files plus Cargo.lock, nothing else. If other unrelated changes are staged/dirty, stop and ask first.
  7. Push: git push -u origin release/vX.Y.Z.
  8. Build release recap from git log <last-tag>..main --oneline (same range used for version signal in step 3). For each commit:

    • Fetch its diff (git show <sha> --stat) and, if a PR number is present, fetch the PR body via gh pr view <number> --json body,title for extra context.
    • Write a 1–2 sentence plain-English summary of what the change actually does from a user's perspective — not a restatement of the commit title. Focus on the observable effect, not the implementation.
    • Categorize case-insensitively by conventional-commit prefix: feat: / feat!: → Features, fix: → Bug fixes, everything else → Improvements. Omit the version-bump commit itself.
    • Omit a section entirely if it has no entries.

    Example output:

    ## Features
    - Tabs can now be dragged between split panes — drop a tab onto any pane
      header to move it there instantly. (#37)
    
    ## Bug fixes
    - The sidebar now correctly highlights the active project even when
      collapsed to icon-only mode.
    - Projects reorder correctly after a drag; the previous ordering glitch
      on drop is fixed.
    
    ## Improvements
    - The split-pane preview is now shown while dragging, giving clearer
      visual feedback before you drop.
  9. Open the PR — title must start with exactly Release (this is what release.yml matches on the squash-merge commit message). Use the recap from step 8 as the top of the body, followed by the release instructions:
    gh pr create --title "Release vX.Y.Z" --base main --head release/vX.Y.Z \
      --body "$(cat <<'EOF'
    <recap sections here>
    
    ---
    Version bump only. Merging triggers the build + draft release; publish it manually to update the Homebrew tap.
    EOF
    )"
  10. Report the PR URL back to the user, and remind them of the two manual gates still ahead: merging this PR (once CI + review pass) and clicking Publish on the resulting draft GitHub Release.

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.