release

Automate software releases by versioning, committing, tagging, and pushing.

17|2|Updated Jun 5, 2025
One-click install
npx skills add https://github.com/AI-Riksarkivet/ra-mcp --skill release-ai-riksarkivet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/AI-Riksarkivet/ra-mcp/tree/main/.claude/skills/release
Command: npx skills add https://github.com/AI-Riksarkivet/ra-mcp --skill release-ai-riksarkivet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the complex and error-prone process of cutting new software releases, ensuring consistency and reducing manual effort.

Core Features & Use Cases

  • Automated Version Bumping: Intelligently determines the next semantic version based on commit history.
  • Release Workflow Orchestration: Manages committing, tagging, and pushing new releases.
  • CI/CD Integration: Triggers subsequent release and publish workflows automatically.
  • Use Case: When you've completed a set of features and bug fixes, you can use this Skill to prepare and publish a new version of your software without manually executing each step.

Quick Start

Use the release skill to cut a new patch version for the project.

Frequently Asked Questions about release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate semantic versioning for git releases?

Automate semantic versioning for git releases by analyzing commit history to determine the next version, bumping the project version file, creating a commit, tagging the release, and pushing changes to the repository. The process requires user confirmation before executing the final release workflow.

How does conventional commit history determine the next release version?

Conventional commit history determines the next release version by parsing commit messages to automatically calculate whether to bump the major, minor, or patch semantic version number for your project.

Can I use automated release workflows to trigger CI/CD pipelines?

Automated release workflows can trigger CI/CD pipelines by automatically pushing new version tags and commits to your repository, which subsequently initiates downstream continuous integration, build, and publish workflows.

Do I need to manually confirm git tags and commits during automated deployment?

You do need to manually confirm git tags and commits during automated deployment, as the release process pauses to require explicit user approval before proceeding with committing, tagging, and pushing changes.

What is the best way to cut a new software patch version after completing bug fixes?

The best way to cut a new software patch version after completing bug fixes is to use an automated release workflow that bumps the version file, commits the changes, tags the release, and pushes to git.