skills.rest
cristoslc
cristoslcCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

swain-release

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

Updated Feb 22, 2026
Search Tags:#automation#git#changelog#versioning#conventional commits#release
One-click install
npx skills add https://github.com/cristoslc/tidegate --skill swain-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: swain-release
Source: https://github.com/cristoslc/tidegate/tree/main/.agents/skills/swain-release
Command: npx skills add https://github.com/cristoslc/tidegate --skill swain-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of releasing new versions of software by automating version bumping, changelog generation, and Git tag creation.

Core Features & Use Cases

  • Automated Version Bumping: Intelligently determines the next version number based on commit history (conventional commits).
  • Changelog Generation: Creates human-readable changelogs from commit messages.
  • Git Tagging: Creates annotated Git tags for new releases.
  • Use Case: After merging a new feature and several bug fixes, you can invoke this Skill to automatically update the version number in your project files, generate a changelog entry, and create a Git tag like v1.2.0.

Quick Start

Use the swain-release skill to cut a new release for the project.

Frequently Asked Questions about swain-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 conventional commits?▼

You can automate version bumping and changelog generation by detecting versioning context from conventional commit history, automatically updating specified project files, and creating an annotated Git tag for the new release.

Can I cut a software release with a dirty Git working tree?▼

Yes, you can cut a release with a dirty working tree, but the automation requires user confirmation before proceeding to ensure uncommitted changes do not interfere with the version bump and Git tag creation.

What is the best way to handle pre-release versions and monorepos during a release?▼

Handling pre-release versions and monorepos involves detecting the specific versioning context within the project structure, generating appropriate changelogs from commits, and applying targeted version bumps to the correct files.

How does automated changelog generation work with conventional commits?▼

Automated changelog generation works by parsing conventional commit messages from your Git history and translating those structured commit types into a human-readable log of changes for the new version.

Do I need to manually specify the next version number before creating a Git tag?▼

No, you do not need to manually specify the next version number; the automation intelligently determines the correct bump based on your commit history and applies it before creating the Git tag.

Why should I use automated release automation instead of manually bumping versions?▼

Automated release automation prevents human error during version bumping, ensures changelogs accurately reflect conventional commit history, and standardizes Git tag creation across your software engineering workflow.

Related Skills

Explore More Software Engineering Skills→
t0labt0lab
2

git-conventional

Enforce Conventional Commits formatting and map commit types to semantic version bumps.

Official
Basic
AndrewDrygaAndrewDryga
28

release

Create semantic version tags from changelogs and push them to Git.

Community
Advanced
mrleeiomrleeio

conventional-commits

Format git commit messages according to the Conventional Commits standard.

Community
Basic
chrislyonschrislyons

git.release.prep

Automates release prep with semantic versioning, changelog generation, and GitHub publishing.

Community
Intermediate