release-cut

Automate Roslyn MCP release pipelines with bump, verify, ship, tag, and reinstall.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/darylmcd/Roslyn-Backed-MCP --skill release-cut
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-cut
Source: https://github.com/darylmcd/Roslyn-Backed-MCP/tree/main/.claude/skills/release-cut
Command: npx skills add https://github.com/darylmcd/Roslyn-Backed-MCP --skill release-cut

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates an end-to-end release process for the Roslyn MCP project, turning a sprawling sequence of checks, version bumps, and git operations into a single repeatable workflow that preserves consistency across releases.

Core Features & Use Cases

  • Coordinated release lifecycle: bump -> verify -> ship -> tag -> reinstall, with checkpointing to re-run from the last successful step.
  • Enforces preflight safeguards (clean working tree, correct branch, up-to-date main) before any release actions.
  • Delegates complex steps to existing skills (/bump, /ship, and /roslyn-mcp:update) to ensure reliability and reuse.

Quick Start

Invoke the release-cut skill with a bump type (patch, minor, or major) to execute the full atomic flow.

Frequently Asked Questions about release-cut

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

FAQPage Schema
How do I automate a git release pipeline from version bump to reinstall?▼

An automated release pipeline coordinates version bumping, verification, shipping, tagging, and reinstalling in a single atomic flow. It transforms Unreleased changelog entries into a tagged, published version while enforcing preflight checks like a clean working tree and an up-to-date main branch.

What is an atomic release workflow for versioning and changelog management?▼

An atomic release workflow executes bump, verify, ship, tag, and reinstall steps sequentially with checkpointing. This ensures reproducible releases by validating changes before finalization and allowing safe re-runs from the last successful step if interruptions occur.

How do I safely re-run a release pipeline if a step fails during tagging?▼

Release pipelines with checkpointed steps enable safe re-runs from the last successful action. Gating checks validate preflight conditions before any release actions execute, ensuring the working tree remains consistent and the release is reproducible.

Do I need a clean git working tree before starting an automated release?▼

Yes, a clean working tree is a required preflight safeguard. The release pipeline enforces gating checks to verify the correct branch, ensure the main branch is up-to-date, and confirm the working tree is clean before performing any version bump or shipping actions.

How do I handle major, minor, and patch release cycles in a single automated flow?▼

Invoke the automated release flow with a specified bump type of patch, minor, or major. The pipeline applies the version bump, moves Unreleased changes into a tagged published version, and validates the changes before finalizing the release.

What's the best way to turn Unreleased changelog entries into a tagged published version?▼

Use an end-to-end release pipeline that applies preflight safeguards, delegates version bumping and shipping to existing skills, and tags the finalized changes. This turns Unreleased changelog entries into a published version while validating the release.