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

release-build

Carries one release component from claim through build, review, and merge against the Marshall store.

Updated Jul 15, 2026
Search Tags:#code review#release coordination#merge automation#ci gates#component workflow#marshall#claim lifecycle
One-click install
npx skills add https://github.com/builtbyberry/marshall-claude-plugin --skill release-build-builtbyberry
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-build
Source: https://github.com/builtbyberry/marshall-claude-plugin/tree/main/marshall/skills/release-build
Command: npx skills add https://github.com/builtbyberry/marshall-claude-plugin --skill release-build-builtbyberry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating a single release component from unclaimed to merged requires retyping the same sequence by hand every time: claim, plan, pressure-test the plan, build, prove tests can fail, change-review, fix, verify fixes, and land. This Skill encodes that sequence once, so a component is carried to merged without skipped gates or lost resume state. ## Core Features & Use Cases - Guided component loop: Runs a nine-step sequence (claim, plan, plan pressure-test, build, prove-can-fail, repo gates, change-review, independent fix verification, landing) against the shared Marshall store. - Composable design: Delegates the claim lifecycle to /marshall:release-topic and lens-based review mechanics to /marshall:change-review, owning only sequencing, the two homeless review gates, and the landing. - Resumable autonomy: Derives resume points from the store plus git (never conversation memory), supports resume and land-only entry modes, and enforces exactly three hard stops with the claim held. - Use Case: Dispatch the loop against a claimed component in autonomous mode; it plans, builds, reviews, fixes, verifies, and merges when clean, or hard-stops and surfaces blockers with the claim still held. ## Quick Start Ask the agent to run /marshall:release-build on a component to carry it from claim to merged.

Frequently Asked Questions about release-build

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

FAQPage Schema
How do I carry a release component from claim to merged?▼

Run /marshall:release-build against the component. It claims the work, plans, pressure-tests the plan, builds, proves tests can fail, runs change-review, verifies fixes independently, and lands the PR, all against the shared Marshall store.

How does release-build resume an interrupted run?▼

It derives the resume point from the Marshall store plus git state, never conversation memory. On ambiguity it re-runs the covering gate, and gates that leave no store footprint are attested out loud rather than silently assumed.

What is the difference between autonomous and supervised merge modes?▼

Autonomous mode merges automatically when the run is clean, suiting dispatched runs. Supervised mode stops at the proposed state so a human merges. Both modes enforce identical gates; an explicit operator instruction overrides the default.

What are the three hard stops in the build loop?▼

The loop hard-stops on a high finding unfixable within the acceptance criteria, CI red after one fix attempt, and genuine scope ambiguity. A hard stop leaves the claim held so resuming costs nothing.

Can release-build fix a pre-existing failure outside my component?▼

No. A pre-existing failure outside your touches triggers hard-stop-and-surface by default. A sanctioned fix becomes a separate claimed, branched, and change-reviewed sibling component, never smuggled into this component's diff.

When should I use land-only entry mode?▼

Use land-only to finish a component already built and change-reviewed by another owner or session. It runs gates through landing while attesting upstream steps, and never skips independent fix verification or the three hard stops.

Related Skills

Explore More Software Engineering Skills→
KhoiwallKhoiwall

verification-before-completion

Run verification commands and record output evidence before completion claims.

Community
Advanced
corbat-techcorbat-tech
1

preflight

Run automated pre-release validation checks on software projects.

Official
Intermediate
AiFirstDevelopmentAiFirstDevelopment

4-quorum

Adjudicates code review findings, applies accepted fixes, and writes a verdict file.

Community
Advanced
bRRRITSCOLDbRRRITSCOLD
2

autonomous-delivery

Automate GitHub issue lifecycle through a dispatch-review-merge loop.

Community
Advanced