agentleFS
crux-clicrux-cli/crux/.claude/skills/release-version/SKILL.md

release-version

Skill0 starsChanged 8 months agoMITView on GitHub

Bump version on main, tag, run release pipeline, then deploy docs. Auto-increments patch if no version given.

  • Commits and pushes

9 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 0 are common, 8 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 8

    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:

    If a version argument was provided, use it.

    line 13
  2. Distinctive:

    If no version argument:

    line 21
  3. Very specific:

    Verify VERSION is greater than CURRENT.

    line 28
  4. Distinctive:

    Commit and push directly to main:

    line 48
  5. Distinctive:

    If the release pipeline fails:

    line 77
  6. Very specific:

    Read failure logs: gh run view <run-id> --log-failed

    line 78
  7. Distinctive:

    Wait for docs deployment:

    line 89
  8. Very specific:

    Update the version in the claude-marketplace repo so the plugin's SessionStart hook installs the correct version:

    line 113
  9. Very specific:

    Update plugins/crux/.claude-plugin/plugin.json — set "version" to "<VERSION>".

    line 121
  10. Very specific:

    Update plugins/crux/hooks/hooks.json — set PLUGIN_VERSION='<VERSION>' in the hook command.

    line 123
  11. Distinctive:

    If tagged but release pipeline failed:

    line 136
  12. Distinctive:

    If already published to PyPI, publish a patch fix instead — PyPI versions cannot be deleted.

    line 143
  13. Distinctive:

    Always verify the release pipeline succeeds before deploying docs

    line 150

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

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

Release Version

Bump the version in pyproject.toml on main, tag the release, run the release pipeline, and deploy docs.

Step 0: Resolve Version

If a version argument was provided, use it. Otherwise, auto-increment:

# Read current version from pyproject.toml
CURRENT=$(grep -m1 '^version' pyproject.toml | sed 's/version = "\(.*\)"/\1/')
echo "Current version: $CURRENT"

If no version argument:

  • Parse CURRENT as MAJOR.MINOR.PATCH
  • Increment PATCH by 1
  • Set VERSION to MAJOR.MINOR.(PATCH+1)

Example: 1.0.1 → 1.0.2

Verify VERSION is greater than CURRENT. If not, abort.

Step 1: Ensure Clean Main

git checkout main
git pull origin main
git status

Working tree must be clean. If not, abort with a message.

Step 2: Bump Version

Update pyproject.toml:

version = "<VERSION>"

Commit and push directly to main:

git add pyproject.toml
git commit -m "chore: bump version to <VERSION>"
git push origin main

Step 3: Tag and Push

git tag v<VERSION>
git push origin v<VERSION>

This triggers .github/workflows/release.yml which:

  • Runs full CI gate
  • Builds sdist + wheel
  • Publishes to PyPI
  • Creates GitHub Release

Step 4: Wait for Release Pipeline

# Find the run triggered by the tag
gh run list --workflow=release.yml --limit=1
gh run watch

If the release pipeline fails:

  1. Read failure logs: gh run view <run-id> --log-failed
  2. Report the failure and stop. Do NOT proceed to docs.

Step 5: Deploy Docs

The docs pipeline does not auto-trigger from GitHub Actions releases. Dispatch manually:

gh workflow run docs.yml -f version=<VERSION>

Wait for docs deployment:

gh run list --workflow=docs.yml --limit=1
gh run watch

Step 6: Verify

# PyPI
pip index versions crux-cli

# GitHub Release
gh release view v<VERSION>

# Docs
echo "Docs: https://crux-cli.github.io/crux/"

Report the version, PyPI status, and docs URL.

Step 7: Update Marketplace Plugin Version

Update the version in the claude-marketplace repo so the plugin's SessionStart hook installs the correct version:

cd ../claude-marketplace
git checkout main
git pull origin main

Update plugins/crux/.claude-plugin/plugin.json — set "version" to "<VERSION>".

Update plugins/crux/hooks/hooks.json — set PLUGIN_VERSION='<VERSION>' in the hook command.

Commit and push:

git add plugins/crux/.claude-plugin/plugin.json plugins/crux/hooks/hooks.json
git commit -m "chore: bump crux plugin version to <VERSION>"
git push origin main
cd ../crux

Rollback

If tagged but release pipeline failed:

git tag -d v<VERSION>
git push origin :refs/tags/v<VERSION>

If already published to PyPI, publish a patch fix instead — PyPI versions cannot be deleted.

Notes

  • This skill operates directly on main — no branch or PR involved
  • The release pipeline requires a PyPI trusted publisher configured in GitHub repo settings
  • The docs pipeline uses mike for versioned documentation
  • Always verify the release pipeline succeeds before deploying docs

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.