release

Coordinate software release stages from changelog generation to final promotion.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/plwsdytcj/opc --skill release-plwsdytcj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/plwsdytcj/opc/tree/main/skills/release
Command: npx skills add https://github.com/plwsdytcj/opc --skill release-plwsdytcj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the complex process of releasing software, ensuring all necessary steps from code to customer communication are coordinated efficiently.

Core Features & Use Cases

  • End-to-End Release Coordination: Manages changelog generation, version bumping, publishing, and post-release announcements.
  • Automated Pre-flight Checks: Verifies preconditions and readiness for a release.
  • Use Case: When a new version of the Paperclip software is ready, this Skill can be invoked to automatically generate the changelog, publish the new version to npm, create tasks for website updates, and draft social media announcements.

Quick Start

Use the release skill to perform a patch release for the current project.

Frequently Asked Questions about release

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

FAQPage Schema
How do I coordinate a software release with changelog generation and npm publishing?

Software release coordination is handled by orchestrating changelog generation, version bumping, and npm publishing into a single synchronized process. It ensures all engineering, marketing, and website updates are executed as idempotent, verifiable steps.

What's the best way to automate cross-functional task creation during a software release?

Automating cross-functional task creation during a software release involves generating tracking items for downstream website updates and social media announcements. This ensures synchronized engineering and marketing updates immediately follow code promotion.

How does version management work with canary publishing and final promotion?

Version management with canary publishing works by applying idempotent and verifiable release steps from initial canary deployment to final promotion. This guarantees the release process remains consistent and recoverable across multiple stages.

Can I use this release process for patch releases in my current project?

Yes, you can use this release process to perform patch releases for your current project. It applies to software development lifecycles requiring synchronized updates across engineering, marketing, and website teams.

How do automated pre-flight checks verify readiness for a software release?

Automated pre-flight checks verify readiness for a software release by validating preconditions before any publishing occurs. This prevents incomplete or inconsistent states from progressing through the version management and promotion pipeline.

Why should I use an orchestrated release process instead of manual versioning?

An orchestrated release process eliminates manual versioning errors by coordinating changelog generation, npm publishing, and cross-functional updates. It provides idempotent steps that ensure every release is verifiable and consistently repeatable.