release

Automate end-to-end release workflows for Claude Code plugins.

1|Updated May 28, 2026
One-click install
npx skills add https://github.com/amoutiers/maxi-superpowers --skill release-amoutiers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/amoutiers/maxi-superpowers/tree/main/.claude/skills/release
Command: npx skills add https://github.com/amoutiers/maxi-superpowers --skill release-amoutiers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing Claude Code plugins is error-prone and repetitive; this skill automates the full release lifecycle from pre-flight checks to publishing, ensuring consistent versioning and changelog discipline.

Core Features & Use Cases

  • Preflight checks to ensure a clean working tree and successful test runs
  • Automatic version bumps across multiple manifests (plugin.json, marketplace.json copies, etc.)
  • CHANGELOG generation with git-cliff and precise marketplace pinning during release

Quick Start

Release a new plugin version by running the release skill against your repository.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate Claude Code plugin release workflows with version bumps and changelog generation?

Automating Claude Code plugin release workflows involves running pre-flight checks, applying version bumps across manifests, generating changelogs, and tagging commits deterministically. This skill coordinates the entire end-to-end lifecycle from local repositories to CI pipelines.

What is the best way to keep marketplace.json and plugin.json versions consistent during a plugin release?

Keeping manifest versions consistent during a plugin release requires automatic version bumps across multiple files like plugin.json and marketplace.json. This ensures deterministic tagging and consistent artifact updates across all configured manifests.

Can I run pre-flight checks and tests before publishing a plugin to the marketplace?

Yes, pre-flight checks ensure a clean working tree and successful test execution before publishing. This skill satisfies requirements for test execution and commit sequencing to guarantee a safe marketplace release.

Does git-cliff work with automated plugin versioning and changelog generation in CI pipelines?

Git-cliff integrates directly into automated plugin versioning workflows for CHANGELOG generation. This skill applies it within CI pipelines to maintain auditable git histories and precise marketplace pinning during releases.

Why do my git histories become inconsistent when releasing multiple plugin manifests manually?

Git histories become inconsistent during manual releases due to human error in commit sequencing and version tagging. Automating dependency updates and commit sequencing ensures auditable git histories and deterministic tagging across all manifests.

When do I need deterministic tagging for local repositories versus CI pipelines?

Deterministic tagging is needed for both local repositories and CI pipelines whenever you require auditable git histories and safe marketplace publishing. This skill applies consistent tagging rules across both environments to prevent release errors.