release

Automate version bumping, changelog generation, and release notes for CLI packages.

Updated Jan 8, 2026

Search Tags:#release management #version control #semver #changelog generation #cli package

Ready to run

npx skills add https://github.com/nutrisari-jeruk/react-vite-template --skill release-nutrisari-jeruk

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/nutrisari-jeruk/react-vite-template/tree/main/.claude/skills/release
Command: npx skills add https://github.com/nutrisari-jeruk/react-vite-template --skill release-nutrisari-jeruk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The release management process for CLI packages can be complex and time-consuming, involving version bumping, changelog generation, and deployment. This skill automates these steps, simplifying the release workflow.

Core Features & Use Cases

Automated Version Bumping: Handles semver version increments based on commit analysis.
Changelog Generation: Automatically generates a changelog based on commits and tags.
Release Notes Preparation: Creates a GitHub release body with changelogs and version history.
Publishing Workflow: Provides a clear step-by-step guide to complete the release.

Quick Start

Run the release skill to automate the release process for the frontier-fe CLI package.

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 for a CLI package?▼

Automating version bumping and changelog generation for a CLI package involves analyzing project commits to apply semantic version increments and automatically generating an updated changelog. This skill handles these tasks by reading project files and triggering based on release-specific keywords.

What is the best way to prepare release notes from commit history before publishing?▼

Preparing release notes from commit history is best handled by automatically aggregating commits and tags to create a structured GitHub release body. This skill analyzes your project's version history to compile these notes and provides a step-by-step publishing workflow.

Does this release management workflow require any external dependencies?▼

This release management workflow does not require external dependencies to function. It operates using internal scripts and directly accesses your project files to perform commit analysis, version bumping, and changelog generation.

Can I use semantic versioning triggers to automate my CLI package release process?▼

Yes, you can use semantic versioning triggers to automate your CLI package release process. The skill specifically monitors for these semver triggers and release-specific keywords to automatically initiate version increments and changelog updates.

How does commit analysis work for determining semantic version increments?▼

Determining semantic version increments through commit analysis works by scanning your project's commit history to identify the nature of changes. The skill uses this analysis to automatically apply the correct semver version bump and prepare the corresponding release notes.

What are the limitations of using scripts for release management automation?▼

Using scripts for release management automation requires granting access to your project files for analysis and modification. The process is currently tailored specifically for CLI packages and depends on recognizing semantic versioning triggers or release keywords to execute accurately.