skills.rest
builtbyberry
builtbyberryOFFICIAL
Explore all skills by this author →
WebsiteGitHub

release-open

Cuts release branches, scaffolds CHANGELOG entries, and opens draft release PRs against the Marshall store.

Updated Jul 15, 2026
Search Tags:#git#changelog#release management#github#mcp#draft pr#release branch
One-click install
npx skills add https://github.com/builtbyberry/marshall-claude-plugin --skill release-open-builtbyberry
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-open
Source: https://github.com/builtbyberry/marshall-claude-plugin/tree/main/marshall/skills/release-open
Command: npx skills add https://github.com/builtbyberry/marshall-claude-plugin --skill release-open-builtbyberry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a release involves repetitive git mechanics — cutting the release branch, scaffolding the CHANGELOG, pushing, and opening a draft PR — plus confirming the release actually exists in the shared Marshall store. This Skill runs that whole sequence in the correct order with hard preflight checks, so a release never starts from a dirty tree, a stale default branch, or an unseeded store entry. ## Core Features & Use Cases - Store-first verification: Confirms the release is seeded in the hosted Marshall store via MCP before touching git, and refuses to proceed if the MCP server is disconnected. - Preflight guardrails: Stops on a dirty working tree, wrong branch, out-of-date default branch, or an already-existing release branch — no auto-fixing. - Git and PR mechanics: Cuts the release branch from the configured pattern, scaffolds the CHANGELOG entry with a theme, pushes, and opens a draft release PR with a wrap-status checklist. - Optional tracker linking: On explicit approval only, links the release to a GitHub milestone or an existing tracker collection (Linear Project/Cycle) via release_update. - Use Case: A maintainer says "start release v0.7.0" — the Skill verifies the release exists in the store, creates release/v0.7.0, scaffolds the CHANGELOG, and opens the draft PR that topic branches will target. ## Quick Start Say "start release v0.7.0" or run /release-open and answer the prompts for the release version and theme.

Frequently Asked Questions about release-open

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

FAQPage Schema
How do I start a new release with the Marshall plugin?▼

Invoke /release-open or say "start release <version>". The Skill confirms the release exists in the Marshall store, runs preflight checks, cuts the release branch, scaffolds the CHANGELOG, and opens a draft release PR.

What happens if the release is not seeded in the Marshall store?▼

The Skill stops and tells you to seed it first with /marshall:release-init (native release_create) or a tracker import — the console importer for GitHub or the web picker at /releases/import. It never seeds the release itself.

Does release-open work if the Marshall MCP server is disconnected?▼

No. The Skill stops immediately and reports the disconnection, because the hosted store is the only source of truth for whether the release exists. It will not proceed from memory or local state.

Why does release-open refuse to run with uncommitted changes?▼

A clean working tree is a hard preflight requirement, along with being on the default branch and up to date with origin. These are hard stops, not warnings — the Skill never auto-stashes, resets, or force-pushes.

Can I link a release to a GitHub milestone or Linear project?▼

Yes, but only on explicit approval. The Skill asks whether to create a new GitHub milestone, link an existing collection by id or URL, or skip. Linking uses release_update and is never done automatically; skip is the default.

What if the release branch or PR already exists?▼

If the release branch already exists locally or remotely, the Skill stops rather than reusing or overwriting it. If a PR already exists for the branch, it surfaces that PR's URL and continues instead of opening a duplicate.

Related Skills

Explore More Software Engineering Skills→
OntoLedgyOntoLedgy

release-planner

Generate prioritized, capacity-aligned feature lists from steering documentation.

Official
Advanced
heyallencaoheyallencao
118

operation/ship

Coordinate final release steps including dependency validation, automated testing, merging, deploying, and health checks.

Community
Advanced
adoreseveradoresever
202

deepwork-tracker

Track deep work sessions locally and generate per-day minute heatmaps.

Community
Intermediate
LazyIsEfficientLazyIsEfficient
15

release-manager

Coordinate monorepo release preparation with git and GitHub CLI.

Official
Advanced