release

Name: release
Availability: InStock
Author: rsultcoding

Automate software releases by bumping versions, generating changelogs, and creating PRs.

Updated Mar 20, 2026

Search Tags:#automation #git #workflow #changelog #versioning #release #PR

Ready to run

npx skills add https://github.com/RsultCoding/rca-archon --skill release-rsultcoding

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/RsultCoding/rca-archon/tree/main/.claude/skills/release
Command: npx skills add https://github.com/RsultCoding/rca-archon --skill release-rsultcoding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the release process for software projects by deriving version bumps, changelog entries, and PR creation from a dev vs main comparison.

Core Features & Use Cases

Detects project stack (pyproject.toml, package.json, Cargo.toml, go.mod) to read and bump the version.
Generates changelog entries from commits on dev since main with PR references.
Updates version files and lockfiles per stack; updates CHANGELOG.md; optionally tags releases and creates a GitHub Release.
Use case: You want to release a new patch version after features are merged into dev.

Quick Start

Run the release skill to create a new release from dev by generating changelog entries, bumping the version, and opening a PR to main.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate version bumping and changelog generation from dev branch commits?▼

Automating version bumping and changelog generation is done by comparing your dev branch against main, deriving the version bump from commit history, updating version files, and creating a PR. This Skill detects your project stack to read and bump versions automatically across Python, Node, Rust, and Go.

What's the best way to create a release PR to main with an auto-generated changelog?▼

Creating a release PR to main with an auto-generated changelog involves reading commits from your dev branch since main, generating changelog entries with PR references, and opening a pull request. This Skill requires a clean dev branch with no uncommitted changes and explicit confirmation before pushing.

Does automated release workflow support Python, Node, Rust, and Go projects?▼

Automated release workflow supports Python, Node, Rust, and Go projects by detecting the project stack through pyproject.toml, package.json, Cargo.toml, and go.mod files respectively. It reads the appropriate version file and updates necessary lockfiles per stack during the release process.

Can I tag releases and create a GitHub Release automatically when merging dev to main?▼

Tagging releases and creating a GitHub Release automatically is supported as an optional step when merging dev to main. This Skill derives version bumps and changelog entries from the dev vs main comparison, updates CHANGELOG.md, and can optionally tag the release and create a GitHub Release.

What are the prerequisites for automating software releases from a dev branch?▼

Prerequisites for automating software releases from a dev branch include having a clean dev branch with no uncommitted changes and a valid project stack file like pyproject.toml or package.json. This Skill enforces a safe workflow by requiring explicit confirmation before pushing and PR creation.

Why does automated release require a clean dev branch with no uncommitted changes?▼

Automated release requires a clean dev branch with no uncommitted changes to enforce a safe workflow and prevent incomplete work from being included in the version bump. This Skill derives the changelog and version bump from the dev vs main comparison, ensuring only committed changes are released.