release

Name: release
Availability: InStock
Author: ormastes

Bump versions across multiple files and automate release workflows.

1|Updated Mar 8, 2026

Search Tags:#automation #git #changelog #versioning #release-management #version-bump

Ready to run

npx skills add https://github.com/ormastes/simple --skill release-ormastes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/ormastes/simple/tree/main/.agents/skills/release
Command: npx skills add https://github.com/ormastes/simple --skill release-ormastes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Version bumps and release processes are scattered across multiple files (e.g., a SDN file, a VERSION file, and hardcoded strings) and require manual edits, risking missed updates, inconsistent changelogs, and delays in shipping.

Core Features & Use Cases

Version bump automation: bump patch, minor, major, or exact X.Y.Z across all version locations.
Cross-file consistency: updates version references in simple.sdn, VERSION, and source files, maintaining consistency.
Release workflow integration: automatically update CHANGELOG.md, create commits, tag releases, and prompt before pushing.

Quick Start

Invoke the release skill with no arguments or with a version specifier (patch, minor, major, or exact X.Y.Z) to perform an automated version bump and release.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate version bumps across multiple files in a monorepo?▼

Automating version bumps across multiple files in a monorepo requires reading the current version and updating all duplicated references, such as VERSION files and source code strings, simultaneously to maintain cross-file consistency before committing and tagging.

What is the best way to update a CHANGELOG and tag a release automatically?▼

Updating a CHANGELOG and tagging a release automatically involves integrating the version bump process with your release workflow to generate changelog entries, create a commit, and apply a tag, prompting before pushing to the remote repository.

Can I specify an exact X.Y.Z version instead of a patch or minor bump?▼

You can specify an exact X.Y.Z version instead of a patch or minor bump by passing the exact version string as an argument, overriding the incremental version bump to update all version locations directly.

Does this release management approach work for single-project repositories?▼

This release management approach works for single-project repositories as well as monorepos by detecting and updating all version data locations within the project, ensuring consistent versioning regardless of repository structure.

Why does my automated release workflow prompt before pushing commits?▼

Automated release workflows prompt before pushing commits to provide a manual confirmation checkpoint, ensuring you review the version bump, changelog updates, and newly created tag before changes are pushed to the remote repository.

What are the limitations of automating version management for hardcoded strings?▼

Automating version management for hardcoded strings requires the tool to correctly identify and parse all version locations across files, and limitations arise if version data formats are non-standard or unrecognized by the bumping process.