skills.rest
albertoirurueta
albertoiruruetaCOMMUNITY
Explore all skills by this author →
GitHub

release

Create release branches and update versioning and documentation for library projects.

Updated Jul 9, 2026
Search Tags:#version control#release automation#gitflow#version increment#library release
One-click install
npx skills add https://github.com/albertoirurueta/ai-catalog --skill release-albertoirurueta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/albertoirurueta/ai-catalog/tree/main/.claude/skills/release
Command: npx skills add https://github.com/albertoirurueta/ai-catalog --skill release-albertoirurueta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the release process for libraries by automating version number changes, creating a release branch, updating documentation, and initiating a pull request for your project.

Core Features & Use Cases

  • Automate Version Changes: Handles incrementing of version numbers from SNAPSHOT to final release version.
  • Create Release Branch: Automates the creation of a release_x.y.z branch.
  • Update Documentation: Updates the version numbers in various documentation files.
  • Open Pull Request: Initiates a pull request against the main branch with all the changes ready to be reviewed.
  • Use Case: When you need to release a new version of your library after completing feature development and fixing any bugs.

Quick Start

To initiate a release, run the /release command in your library repository.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate library release version increments from a SNAPSHOT to a final version?▼

This Skill automates library release version increments by updating version numbers from SNAPSHOT to final release versions, creating a release branch, and updating documentation before merging into the main branch.

What is the best way to create a release branch and open a pull request using gitflow?▼

The best way to create a release branch using gitflow is running the release command from the develop branch, which automates branch creation, updates versioning in pom.xml, and opens a pull request against main.

Do I need to run the release command from the develop branch to update pom.xml?▼

Yes, you must run the release command from the develop branch. It requires this gitflow starting point to properly increment pom.xml versioning and prepare changes for the main branch.

Does release automation work with Maven library projects to update documentation?▼

Yes, release automation works with Maven library projects by parsing pom.xml to increment versions and automatically updating version numbers across various documentation files.

What are the limitations of automating version control for library releases?▼

A key limitation of automating version control for library releases is the strict requirement to execute the command from the develop branch, ensuring proper gitflow before merging to main.

Related Skills

Explore More Software Engineering Skills→
alexanderopalexanderop

using-git-worktrees

Create isolated git worktrees for feature branches with safety checks.

Community
Advanced
NVIDIANVIDIA
22.1k

nemoclaw-maintainer-cut-release-tag

Automates semver release tagging and version string updates for NemoClaw.

Official
Advanced
dr-codedr-code

release-check

Run pre-release verification checks and write a versioned release assessment report.

Community
Advanced
oracleoracle
21.7k

build-native-image-maven

Build GraalVM native images for Java applications using the native-maven-plugin.

Official
Intermediate