release-assistant

Automate release workflows with linting, testing, version bumps, and tags.

1|Updated Nov 2, 2025

Search Tags:#git #versioning #CI/CD #release #semver #tagging

Ready to run

npx skills add https://github.com/fubira/claude-code-settings --skill release-assistant

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-assistant
Source: https://github.com/fubira/claude-code-settings/tree/main/skills/release-assistant
Command: npx skills add https://github.com/fubira/claude-code-settings --skill release-assistant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and guards release workflows by enforcing lint/tests, analyzing commits for semver, performing version bumps, and creating tags.

Core Features & Use Cases

Pre-flight checks: clean working tree, lint, tests, type check
Version analysis and bump calculation using Conventional Commits rules
Commit the bump and create tag, then push
Changelog summary and post-release notes (for context)

Quick Start

After finalizing changes, say "リリースして" or "release" to start the automated release workflow.

Frequently Asked Questions about release-assistant

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

FAQPage Schema

How do I automate my software release workflow with version bumping and tagging?▼

Release workflows automate pre-flight checks, version bumping using Conventional Commits rules, and tag creation. This Skill enforces linting, testing, and type checking, then calculates MAJOR, MINOR, or PATCH bumps, commits the version change, creates a git tag, and pushes to your remote repository for npm, PNPM, and Bun projects.

Does this work with my package manager—npm, PNPM, or Bun?▼

Yes, this Skill supports npm, PNPM, and Bun projects. It integrates with your existing project structure and applies Conventional Commits analysis to determine version increments consistently across all three package managers.

How does Conventional Commits determine version changes during release?▼

Conventional Commits parse commit messages to categorize changes: breaking changes trigger MAJOR bumps, new features trigger MINOR bumps, and fixes trigger PATCH bumps. The Skill analyzes commits since the last tag and calculates the appropriate semver increment automatically.

What checks run before a release is allowed to proceed?▼

Pre-flight checks verify a clean working directory with no uncommitted changes, passing lint rules, successful test execution, and type checking. All checks must pass before the Skill allows version bumping and tagging to proceed.

Can I review and confirm changes before the release pushes to my repository?▼

Yes, the Skill requires explicit user confirmation before applying version changes and before pushing commits and tags to your remote repository, giving you full control over the release process.

What happens after the version is bumped and tagged?▼

After confirmation, the Skill commits the version bump, creates a git tag, and pushes both to your remote. It also provides a changelog summary and post-release notes for reference and communication.