release

Automate version bumps, changelog updates, git tagging, and code pushes.

11|2|Updated Jan 31, 2026

Search Tags:#git #version control #github #continuous integration #software release

Ready to run

npx skills add https://github.com/rioX432/CivitDeck --skill release-riox432

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/rioX432/CivitDeck/tree/main/.claude/skills/release
Command: npx skills add https://github.com/rioX432/CivitDeck --skill release-riox432

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, github, and includes scripts (resource) components.

What problem does it solve?

Manages software release processes with a single command, eliminating the need for multiple manual steps.

Core Features & Use Cases

Version Bump: Automatically increments software version numbers across different platforms.
Change Log Update: Updates the CHANGELOG.md file with the new version's details.
Tagging & Pushing: Creates a git tag and pushes the commit to trigger the release workflow.
Use Case: For a software developer looking to automate the release process of an application, this skill reduces the time spent on repetitive tasks like updating version numbers and pushing code.

Quick Start

Use the release skill to update the version to the next patch release: 'release patch'

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate a software release with a single git command?▼

Automating a software release is achieved by triggering a command that bumps versions, updates the change log, creates a git tag, and pushes the commit to trigger continuous integration workflows.

What is the best way to update version numbers and push code for a new release?▼

Updating version numbers and pushing code for a new release is best handled by an automation script that increments the version across platforms, updates CHANGELOG.md, and pushes the git tag automatically.

Do I need GitHub access to automate git tagging and version bumps?▼

Yes, you need GitHub access and git installed to perform actions on the repository, as the automation requires pushing commits and tags to trigger the continuous integration release workflow.

How does a single command update the CHANGELOG.md file during a release?▼

The single command updates the CHANGELOG.md file by automatically appending the new version's details during the release process, eliminating manual change log editing before pushing the git tag.

Can I use this automation for continuous integration workflows?▼

Yes, you can use this automation for continuous integration workflows, as it is specifically designed to push code and git tags that trigger the release process within your established development pipeline.

What are the limitations of automating software releases with a single command?▼

The limitation of automating software releases is that it depends entirely on git and GitHub infrastructure, meaning repository access and continuous integration setup must be pre-configured for the command to execute successfully.