release-deploy

Drives release cut-over merges, deploy monitoring, smoke checks, and tagging against the Marshall store.

Updated Jul 15, 2026
One-click install
npx skills add https://github.com/builtbyberry/marshall-claude-plugin --skill release-deploy-builtbyberry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-deploy
Source: https://github.com/builtbyberry/marshall-claude-plugin/tree/main/marshall/skills/release-deploy
Command: npx skills add https://github.com/builtbyberry/marshall-claude-plugin --skill release-deploy-builtbyberry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating the final cut-over of a release — merging the PR, watching the deploy, smoke-checking production, monitoring the window, and tagging — is error-prone when state lives in conversation memory or repo-local files, especially across sessions, machines, and agents. This Skill drives the entire ship flow against the shared Marshall store so every step is recorded, resumable, and never re-executed. ## Core Features & Use Cases - Deploy mode: Merge the release PR, watch a Laravel Cloud (or manual) deploy, run an HTTP smoke check, monitor a timed window, and tag the merge commit — each step recorded via set_deploy_step. - Tag mode: For releases that ship as tagged packages (Packagist), drive merging → dating → tagging → releasing → done via set_ship_step, with the operator running irreversible git/GitHub commands. - Resumability and safety gates: release_get is read on every invocation so a resumed run never re-merges or re-deploys; the store's readiness gate blocks shipping when unresolved high-severity findings exist. - Use Case: After /marshall:release-wrap clears a release, invoke this Skill to merge PR #42, watch the Laravel Cloud deploy, smoke-check the production URL, monitor for 30 minutes, and tag v0.21.0 on the merge commit — all recorded on the store's Deploy record. ## Quick Start Say "deploy the release" or run /release-deploy to start the gated cut-over flow for the current release.

Frequently Asked Questions about release-deploy

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

FAQPage Schema
How do I deploy a release with the Marshall plugin?

Invoke /release-deploy after release-wrap completes. The skill reads the Deploy record from the Marshall store, trips the readiness gate, has the operator merge the release PR, then watches the deploy, smoke-checks production, monitors the window, and tags the merge commit.

What is the difference between deploy mode and tag mode?

Deploy mode ships by merging and watching a production deploy with smoke and monitor steps. Tag mode ships a tagged package where Packagist syncs off the tag, progressing through merging, dating, tagging, releasing, and done. The mode is set by wrap.mode in .claude/release-config.json.

Can I resume a release deploy after an interrupted session?

Yes. The skill reads deploy.step from the Marshall store on every invocation and resumes from the recorded step. A deploy already at deploying is never re-merged or re-triggered, and a monitor window resumes from its recorded start time.

Why does set_deploy_step return deploy_blocked?

deploy_blocked means the readiness gate refused the deploy because the release has unresolved high-severity findings. Resolve them via /marshall:release-wrap or resolve_finding first, then retry the deploy step.

What happens when the production smoke check fails?

The record stays at smoke or monitor with smoke_ok false and verdict rollback-needed; it is never advanced to done. The skill surfaces investigation and rollback options, such as reverting the merge or rolling back via the Laravel Cloud dashboard, and waits for a human decision.

Does the skill run git tag or gh release create itself?

No. Irreversible commands like git tag, git push, gh pr merge, and gh release create are surfaced for the operator to run. The skill only records the confirmed evidence, such as merge SHA, tag, and release URL, on the store.