release

Generate bilingual changelogs, version tags, and GitHub release notes.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/ousiass/claude-config --skill release-ousiass
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/ousiass/claude-config/tree/main/skills/release
Command: npx skills add https://github.com/ousiass/claude-config --skill release-ousiass

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the entire release process, from generating changelogs and version tags to creating GitHub release notes, saving developers significant time and ensuring consistency.

Core Features & Use Cases

  • Automated Changelog Generation: Creates日英併記 (Japanese/English bilingual) changelogs based on commit history and PRs.
  • Version Tagging & Pushing: Automatically creates and pushes Git tags for new releases.
  • GitHub Release Creation: Generates GitHub releases with attached artifacts if specified.
  • Use Case: After merging a new feature branch, you can run /release to automatically generate a changelog entry, tag the release, and create a GitHub release, ready for deployment.

Quick Start

Run the release skill to create a patch release for the current version.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate changelog generation and version tagging for my GitHub releases?

The release process determines version bumps by classifying collected commit history and merged pull requests. It analyzes the nature of code changes to automatically decide whether a patch, minor, or major version increment is appropriate.

How do I generate a bilingual changelog from Git commit history?

Creating GitHub releases with this skill requires both Git and GitHub CLI installed and configured. These command-line tools are necessary for the local version control operations and remote repository interactions needed to push tags and publish release notes.

What's the best way to manage the software release lifecycle using Git and GitHub CLI?

Managing the release lifecycle with Git and GitHub CLI involves collecting commit history, determining version bumps, and creating remote releases. This skill orchestrates these steps to automatically generate changelogs, push version tags, and create GitHub release artifacts.

Does this automated release process require a specific project structure or configuration?

The automated release process relies on your project's existing commit history and merged pull requests to classify changes. It requires a Git repository with a configured GitHub CLI remote to successfully generate changelog entries, push tags, and create remote releases.