Skills Guide

Release Workflow

VerifiedCaution

Automate version bump, commit, tag, and GitHub release creation.

Download and use
Sby Skills Guide Bot
DevOpsIntermediate
7/22/2026
Claude Code
#release-management#versioning#git#github-releases#changelog

Recommended for

Backend developerClaude CodeDevOps engineerGit automation

Automated summary

Automates the qsv-stats release workflow: bumping the version in Cargo.toml, committing, tagging, pushing, and creating the GitHub release.

Strengths

  • Chains all seven release steps (clean-tree check, bump, commit, tag, push, GitHub release) through explicit commands
  • Generates a release summary by grouping commits under conventional prefixes (perf, feat, fix, refactor, chore, docs)
  • Builds in guardrails: stops on uncommitted changes and shows the summary for review before publishing
  • Honours repo conventions, including the #:version marker, tags without a v prefix, and checking existing tags

Limitations

  • Tightly coupled to one Rust project (qsv-stats): Cargo.toml path and tag convention are hardcoded
  • Requires git plus an authenticated gh CLI pointed at the remote
  • Does not cover publishing to crates.io, maintaining a separate CHANGELOG, or running tests beforehand
When to use it

Use it when a new qsv-stats version is ready and you want a repeatable path from version bump to GitHub release.

When not to use it

Avoid it for a different repository or language, or when you want to review and approve each release step manually.

Security analysis

Caution
Quality score86/100

This is a legitimate release automation skill with no destructive, exfiltration, or obfuscated behavior. It is rated caution because it performs powerful and largely irreversible git/GitHub operations, especially pushing tags and creating releases, with limited confirmation guardrails.

Findings
  • •Performs remote-affecting operations (`git push`, `git push --tags`, `gh release create`) that publish commits, tags, and releases without explicit per-command confirmation.
  • •Pushes the commit and tag before the release summary is shown for user review; review only occurs before GitHub release creation, so tagged history may be published before approval.
  • •No `allowed-tools` are declared even though the workflow requires shell, git, and GitHub CLI execution, leaving tool permissions unscoped.
  • •Automatically edits `Cargo.toml` and creates commits/tags without validating that the requested version is semver-compliant, newer, or unused.
How this analysis is made

Examples

Release with explicit version
/release 0.47.0
Release without version argument
Cut a new release of qsv-stats
Check tag convention first
Run the release skill, but check the last few tags first to confirm the naming convention

name: release description: Bump version, commit, tag, and create a GitHub release disable-model-invocation: true

Release

Automate the qsv-stats release workflow.

Arguments

The user should provide the new version number (e.g., 0.47.0). If not provided, ask for it.

Workflow

  1. Verify clean state: Run git status to ensure the working tree is clean
  2. Bump version: Update the version in Cargo.toml on the line marked with #:version
    • The line looks like: version = "0.46.0" #:version
    • Only change the version string, preserve the comment marker and alignment
  3. Generate release summary: Run git log --oneline from the last tag to HEAD and categorize commits:
    • perf: — Performance improvements
    • feat: — New features
    • fix: — Bug fixes
    • refactor: — Refactoring
    • chore: — Maintenance
    • docs: — Documentation
  4. Commit: Create a commit with message v X.Y.Z release
  5. Tag: Create a git tag X.Y.Z (no v prefix — matches existing tag convention)
  6. Push: Push the commit and tag with git push && git push --tags
  7. GitHub release: Create a release via gh release create X.Y.Z --title "X.Y.Z" --notes "<release summary>"

Notes

  • Check existing tags with git tag --sort=-v:refname | head -5 to confirm the naming convention
  • If there are uncommitted changes, warn the user and stop
  • Always show the release summary for user review before creating the GitHub release

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/release-workflow-mrwak98y/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/release-workflow-mrwak98y' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/release-workflow-mrwak98y/download' --output '.skill-downloads/release-workflow-mrwak98y/SKILL.md.part' && mv '.skill-downloads/release-workflow-mrwak98y/SKILL.md.part' '.skill-downloads/release-workflow-mrwak98y/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/release-workflow-mrwak98y/SKILL.md' && test -s '.skill-downloads/release-workflow-mrwak98y/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/release' && cp -R '.skill-downloads/release-workflow-mrwak98y' '.claude/skills/release'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/release-workflow-mrwak98y'

openskills read 'release-workflow-mrwak98y'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/release-workflow-mrwak98y/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

Configure a Chat Channel with SecretRefs

DevOps

Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.

Claude CodeCodexintermediateSafe 387,940
Skills Guide Bot

Investigate ClickHouse CI Failures

DevOps

Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.

Claude CodeadvancedSafe 49,516
Skills Guide Bot

Ansible PR Review

DevOps

Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.

Claude CodeintermediateSafe 70,491
Skills Guide Bot