release

Create a release branch and update version metadata for semver releases.

5|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/ably/ably-ai-transport-js --skill release-ably
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/ably/ably-ai-transport-js/tree/main/.claude/skills/release
Command: npx skills add https://github.com/ably/ably-ai-transport-js --skill release-ably

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual overhead and risk from cutting a new software release by coordinating version updates, lockfile refreshes, changelog generation, and review staging in one controlled workflow.

Core Features & Use Cases

  • Release branch creation: Creates a dedicated release branch for a patch, minor, major, or exact semver version.
  • Version synchronization: Updates the repository version in package metadata and source version files so the release stays consistent.
  • Lockfile refresh and validation: Regenerates root and demo lockfiles, runs precommit checks, and surfaces unusual diff churn before review.
  • Changelog preparation: Regenerates the release entry in CHANGELOG.md and stages it for human review.
  • Use Case: A maintainer needs to ship the next version safely, keep demo apps aligned, and prepare a clean review bundle without committing changes automatically.

Quick Start

Use the release skill to cut the next version branch, update the repository files, and stage the changes for human review.

Frequently Asked Questions about release

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

FAQPage Schema
How do I cut a release branch with semver version bumps and changelog updates?

Cutting a release branch with semver version bumps creates a dedicated branch, updates package.json and src/version.ts, regenerates lockfiles, and prepares CHANGELOG.md. The workflow stages all changes for human review without auto-committing.

What's the best way to automate patch, minor, and major release versioning across package.json and lockfiles?

Automating patch, minor, and major release versioning synchronizes version metadata across package.json, source files, and lockfiles. It runs preflight checks on a clean main branch and regenerates root and demo lockfiles before staging changes.

Does the release workflow update pnpm lockfiles and validate diffs before committing?

The release workflow updates pnpm lockfiles by regenerating root and demo lockfiles, runs precommit checks, and surfaces unusual diff churn. It validates changes and stages them for review without pushing to the remote repository.

Can I prepare a changelog and version bump for an exact semver release without pushing commits?

You can prepare a changelog and version bump for an exact semver release without pushing commits. The workflow regenerates the release entry in CHANGELOG.md, updates versions, and stages the bundle locally for human review.

Why does my release branch creation require a clean main branch preflight check?

Release branch creation requires a clean main branch preflight check to ensure the repository is in a stable state before version synchronization. This prevents uncommitted changes from polluting the release bundle during lockfile regeneration.

What files are updated when cutting a semver release branch for a JavaScript repository?

Cutting a semver release branch updates package.json, src/version.ts, root and demo lockfiles, and CHANGELOG.md. It coordinates these file updates to keep the repository version consistent across metadata and source files.