skills.rest
blueraai
blueraaiOFFICIAL
Explore all skills by this author →
GitHub

release

Automate Node.js releases by deriving version bumps from commit history and coordinating GitHub Actions tagging.

Updated Aug 23, 2026
Search Tags:#automation#versioning#release#GitHub Actions#CI#conventional-commits
One-click install
npx skills add https://github.com/blueraai/claude-code-anywhere --skill release-blueraai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/blueraai/claude-code-anywhere/tree/main/.claude/skills/release
Command: npx skills add https://github.com/blueraai/claude-code-anywhere --skill release-blueraai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the release process for software projects by deriving version bumps from commit history, updating package metadata, and coordinating GitHub Actions during release.

Core Features & Use Cases

  • Auto-detect version bumps: Determine patch, minor, or major releases from conventional commits and commit messages.
  • CI-integrated tagging: Push tags and create GitHub Releases after successful CI.
  • Pre-flight safeguards: Validate clean working directory and ensure release tasks run with minimal manual steps.

Quick Start

Use the release skill to start an automated release for your project. Prefix commands with SKILL=release, e.g. SKILL=release bun run release. To force a specific bump, use SKILL=release bun run release:patch or release:minor or release:major.

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 from conventional commits in Node.js?▼

Automate version bumps from conventional commits by parsing commit history to determine patch, minor, or major increments, then updating package metadata and coordinating CI-driven tagging via GitHub Actions.

How do I publish GitHub Releases automatically after a successful CI build?▼

Publish GitHub Releases automatically after CI by integrating a release workflow that pushes Git tags and creates releases directly within your configured GitHub Actions pipeline.

Do I need conventional commits to trigger automated CI tagging for my releases?▼

Yes, conventional commits are required to trigger automated CI tagging. The release process derives version bumps from commit messages, meaning non-conventional messages prevent proper patch, minor, or major release detection.

Can I force a specific version bump instead of relying on commit history?▼

Force a specific version bump instead of relying on commit history by executing targeted package scripts like release:patch, release:minor, or release:major prefixed with the release skill command.

Why does my automated release workflow fail with uncommitted changes?▼

Your automated release workflow fails with uncommitted changes because the process includes pre-flight safeguards that require a clean working directory to safely update package metadata and push tags.

Related Skills

Explore More Software Engineering Skills→
ereticaeretica

build-and-release

Automate version bumping, commit, tag, and push to GitHub for releases.

Community
Advanced
bmad-code-orgbmad-code-org
51.7k

bmad-os-release-module

Automates npm release process including changelog drafting, versioning, git tagging, publishing, and GitHub releases.

Official
Advanced
marquesfelipmarquesfelip

automated-versioning

Automate semantic version bumps from conventional commits in CI/CD pipelines.

Community
Advanced
amanmprojectsamanmprojects

bump-version

Bump semantic versions in package.json and create v-prefixed Git tags.

Community
Intermediate