release-management

Coordinate release preparation, versioning, and git tag creation for Skyline projects.

17|2|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/ProteoWizard/pwiz-ai --skill release-management-proteowizard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-management
Source: https://github.com/ProteoWizard/pwiz-ai/tree/main/claude/skills/release-management
Command: npx skills add https://github.com/ProteoWizard/pwiz-ai --skill release-management-proteowizard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams manage software releases by providing a clear, repeatable process for version numbering, release notes generation, and tag management.

Core Features & Use Cases

  • Version Numbering & Tagging: Standardizes version formats and git tag creation per release type.
  • Release Notes & Communication: Generates concise release notes and communicates changes to stakeholders.
  • Release Readiness Checks: Verifies build viability, dependency updates, and installer references.

Quick Start

Follow ai/docs/release-guide.md to begin release prep, including versioning, notes, and tag creation.

Frequently Asked Questions about release-management

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

FAQPage Schema
How do I standardize version numbering and git tags for major, daily, and patch releases?

To standardize version numbering and git tags, this release management skill applies formal version formats and git tag conventions across major, daily, and patch releases, ensuring repeatable and consistent versioning for your software projects.

What is the best way to generate centralized release notes from recent code changes?

Generating centralized release notes is handled by this skill through summarizing code changes into concise release notes, which are then used to communicate updates and version changes to stakeholders effectively.

How do I verify release readiness before creating an installer and tagging a build?

Verifying release readiness involves checking build viability, confirming dependency updates, and validating installer references before proceeding with tag creation and installer generation to ensure a stable release.

Can I use this release preparation workflow for daily builds, or is it only for major releases?

Yes, you can use this release preparation workflow for daily builds, as it explicitly supports versioning, notes generation, and installer tagging across major, daily, and patch releases alike.

What do I need to start coordinating software releases with this process?

To start coordinating releases, you need to follow the release guide documentation to begin release preparation, which includes setting up versioning, generating notes, and managing git tag creation.