releasing-plugins

Coordinate automated plugin release workflows with version bumps, changelogs, and tags.

2|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/lwndev/lwndev-marketplace --skill releasing-plugins
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: releasing-plugins
Source: https://github.com/lwndev/lwndev-marketplace/tree/main/.claude/skills/releasing-plugins
Command: npx skills add https://github.com/lwndev/lwndev-marketplace --skill releasing-plugins

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

What problem does it solve?

This Skill guides teams through a two-phase plugin release workflow, ensuring releases are prepared in Phase 1 and properly tagged in Phase 2 with a stop-hook enforced gate.

Core Features & Use Cases

  • Two-phase release workflow: pre-merge preparation and post-merge tagging to align with governance.
  • State management and gating: uses .sdlc/releasing markers to track release progress and enforce phase completion.
  • Quality checks: identifies plugin scope, generates changelog, builds health checks, and assists with PR creation and tagging to publish a new version.
  • Real-world use: a team releasing lwndev-sdlc plugins can streamline version bumps, changelog consolidation, and tag pushes with minimal manual steps.

Quick Start

Initiate Phase 1 by choosing the plugin to release and follow the guided prompts to prepare the release.

Frequently Asked Questions about releasing-plugins

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

FAQPage Schema
How do I automate plugin releases with version bumping and changelog generation?

Automated plugin releases coordinate version bumping, changelog generation, and release tagging into a guided workflow. This process manages pre-merge preparation and post-merge tagging to ensure reproducible package releases.

What is a two-phase release workflow for plugins?

A two-phase release workflow splits plugin publishing into pre-merge preparation and post-merge tagging. It uses state markers and a stop-hook gate to enforce phase completion, ensuring changes are validated before tags are pushed.

How do I generate changelogs and tag releases across multiple plugin packages?

Generating changelogs and tagging releases across packages involves identifying plugin scope, validating changes, and building health checks. The workflow consolidates changelogs and pushes tags to publish new versions with minimal manual steps.

Do I need jq installed to automate version bumps and release tagging?

Yes, jq is required as a dependency to automate version bumps and release tagging. The scripts use jq to parse and manage state markers in the .sdlc/releasing directory for correct sequencing.

How does the stop-hook enforce phase gates during plugin releases?

The stop-hook enforces phase gates by validating state markers stored in the .sdlc/releasing directory. It prevents post-merge tagging from proceeding until pre-merge preparation and health checks are fully completed.

Can I use this automated release workflow for individual plugin packages?

Yes, the workflow supports releasing individual plugin packages within a repository. It guides users through identifying the target plugin, validating changes, and pushing PRs or tags specific to that package.