release-init

Creates a project and release directly in the shared Marshall store via MCP tools.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams need a way to bootstrap a new project and release in the shared Marshall store without importing from an external tracker first, while avoiding duplicate projects, duplicate releases, and broken tracker links. ## Core Features & Use Cases - Born-in-the-store creation: Calls project_create and release_create directly so the release exists in Marshall immediately, with no import step. - Idempotent resume: Probes with release_get before creating, so re-running against an existing release resumes instead of duplicating it. - Optional tracker linking: Attaches a repo and tracker_kind (GitHub, Linear, or Jira label) to the project; on a resolving tracker, release_create also creates the release's collection (GitHub milestone or Linear Project) server-side. - Use Case: An operator says "start a release v0.5.0 for the payments project" — the skill surveys existing projects, reuses or creates the project, creates the release with theme and out-of-scope notes, and reports whether a tracker collection was linked. ## Quick Start Ask the agent to bootstrap a new release in Marshall by naming the project, a version or slug like v0.5.0, and a one-line theme.

Frequently Asked Questions about release-init

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

FAQPage Schema
How do I create a release in Marshall without a GitHub milestone?

Use the born-in-the-store path: call project_create to resolve-or-create the workspace project, then release_create with a version-or-slug, theme, and optional out_of_scope. The external tracker link is optional and the store remains the source of truth.

What happens if I run release-init twice for the same release?

The skill probes with release_get before creating, so a re-run resumes the existing release instead of duplicating it. release_create is also refused on an existing slug, so no second release or tracker collection is created.

Does release_create also create a GitHub milestone or Linear project?

Yes, on a project whose tracker resolves, release_create creates the release's collection server-side and stores the link. Linear additionally requires tracker_team set to the team UUID, and both trackers depend on server-side feature flags.

What if project_create and release_create are not available on the MCP server?

The skill fails closed and points at the import seam instead of improvising. Build the collection in the tracker and import it via php artisan srm:import-release for GitHub or the web picker at /releases/import for Linear.

Why did my Linear collection fail to create during release init?

The likeliest cause is a missing or key-shaped tracker_team — Linear's API requires a team UUID on every create, not the key shown in its UI. The release itself is still created with a null link, and the failure is logged rather than retried.