Skip to content
Skills Library
DevOps & cloud · Automation

release

/release

Cut a new release of ra-mcp. Determines the next version from the commit history since the last tag, bumps pyproject.toml, commits, tags, and pushes. Use when: "make a release", "cut a release", "release", "bump version", "tag a new version", "publish a new version".

Repository
ra-mcp ↗
Licence
Apache-2.0
Last repository change
21.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 21.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Cut a new release of ra-mcp. Determines the next version from the commit history since the last tag, bumps pyproject.toml, commits, tags, and pushes. Use when: "make a release", "cut a release", "release", "bump version", "tag a new version", "publish a new version".

Triggers from the description

make a releasecut a releasereleasebump versiontag a new versionpublish a new version
Original author description

Cut a new release of ra-mcp. Determines the next version from the commit history since the last tag, bumps pyproject.toml, commits, tags, and pushes. Use when: "make a release", "cut a release", "release", "bump version", "tag a new version", "publish a new version".

How it works

  1. Workflow
  2. Rules
Original SKILL.md headings · 53 lines, 349 words
SKILL.md preview
---
name: release
description: >
  Cut a new release of ra-mcp. Determines the next version from the commit
  history since the last tag, bumps pyproject.toml, commits, tags, and pushes.
  Use when: "make a release", "cut a release", "release", "bump version",
  "tag a new version", "publish a new version".
---

# Release Skill

Cut a new release for the ra-mcp project.

## Workflow

1. **Determine current state** — run these in parallel:
   - `git tag --sort=-v:refname | head -5` to find the latest tag
   - `grep '^version' pyproject.toml | head -1` to find the current version
   - `git log --oneline $(git describe --tags --abbrev=0)..HEAD` to list commits since the last tag

2. **Decide the version bump** — follow semver based on conventional commits:
   - **patch** (0.x.Y): only `fix`, `refactor`, `perf`, `docs`, `style`, `test`, `build`, `ci`, `chore`
   - **minor** (0.X.0): any `feat` commit
   - **major** (X.0.0): any commit with `!` or `BREAKING CHANGE` footer
   - If the user specified a version, use that instead

3. **Confirm with the user** — show:
   - Current version and proposed next version
   - Summary of commits going into the release
   - Ask for approval before proceeding

4. **Cut the release** — run:
   ```bash
   make release VERSION=<version>
   ```
   This bumps `pyproject.toml`, commits, tags, and pushes. The tag push
   triggers two CI workflows in parallel: `release.yml` (changelog + GitHub
   Release) and `publish.yml` (Docker build, push, sign, and attestations).

5. **Monitor CI workflows** — after the tag push, watch both workflows:
   - Run `gh run list --limit 5` to find the triggered runs
   - Poll with `gh run view <run-id>` until both "Release" and "Publish"
     workflows complete (check every ~30 seconds)
   - If either workflow fails, run `gh run view <run-id> --log-failed` to
     get the error details and report them to the user
   - Only proceed to the report step once both workflows succeed

6. **Report** — confirm the tag was pushed and link to the GitHub releases page:
   `https://github.com/AI-Riksarkivet/ra-mcp/releases`

## Rules

- ALWAYS confirm the version with the user before running `make release`
- NEVER skip the confirmation step
- If there are uncommitted changes, warn the user and stop
- If there are no new commits since the last tag, tell the user and stop
- When making any git commits (e.g., committing uncommitted changes before
  releasing), follow the conventions in `.claude/commands/commit.md` —
  in particular: no co-author lines, no Claude attribution, clean
  conventional commit format

Versions

RepositoryScoreLicence
This page · ai-riksarkivet/ra-mcp100Apache-2.0
josephfung/curia100MIT
max-sixty/worktrunk100MIT
gtapps/hermitd100MIT
gtapps/hermitd100MIT
anthony-chaudhary/fak100Apache-2.0
tractorjuice/arc-kit100MIT
drvoss/everything-copilot-cli100MIT
sma1lboy/rove100MIT

Database snapshot: 13.11.2026 · package version 337c7c1a0cc0 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100release-cli
    Release a new version of the pd CLI. Runs tests, bumps version, creates git tag, and pushes to remote. Use when releasing a new CLI version.
  • 100version-release
    Use when bumping version, creating a release tag, or pushing a version tag. Triggers on "version up", "release", "tag push", "bump version".
  • 100nvidia-nemoclaw-maintainer-cut-release-tag
    Cut a new semver release — bump all version strings via bump-version.ts, open a release PR, and after merge tag main and push. Use when cutting a release, tagging a version, shipping a build, or preparing a deployment. Trigger keywords - cut tag, release tag, new tag, cut…
  • 100release-ccs
    Publish a new ccfullsearch release. Bumps version, updates CHANGELOG, commits, tags, pushes, and waits for CI + cargo-dist. Use when user says "release", "publish", "new version", or "зарелизь".
  • 100ship-release
    Use when the user asks to release, ship, publish, cut or tag a version of a project ("release v0.2.0", "ship a patch", "bump and publish"). Bumps every version manifest, updates CHANGELOG and README badges, commits, lands it directly or through a pull request (pre-PR check,…
  • 100pypi-release
    Release a new seckit version to PyPI from this repository. Use when the user asks to publish, release, ship or tag a new version of seckit, bump the version, or check or fix the PyPI publish workflow.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.