claude-run-train

Coordinates multi-repo release trains with draft PRs, review, and sequential merges.

2|1|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/Consiliency/agent-harness --skill claude-run-train-consiliency
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: claude-run-train
Source: https://github.com/Consiliency/agent-harness/tree/main/skills-src/claude/claude-run-train
Command: npx skills add https://github.com/Consiliency/agent-harness --skill claude-run-train-consiliency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating a release that spans multiple repositories is error-prone: PRs must open in dependency order, merges must respect upstream changes, and a failed downstream integration can silently break the train. This Skill provides the Claude Code entry point to the phase-loop run-train coordinator, which automates that entire cross-repo workflow. ## Core Features & Use Cases - Topo-ordered draft PRs: Opens draft PRs across all train nodes in dependency order after a preflight check, stopping before any PR is opened if preflight fails. - Governed merge phase: With the --governed flag, runs train-level review, then merges upstream nodes first and re-verifies each downstream node against the upstream merged SHA. - Crash-resumable ledger: Inspect state with phase-loop train-status and resume interrupted runs; already-merged nodes are skipped and blocked nodes retried. - Use Case: You maintain five services that must ship together. Define a train roadmap with Nodes, Depends on, and Channel fields, then let the coordinator open all draft PRs, gather train-level review, and merge sequentially with downstream re-verification. ## Quick Start Ask Claude to run the release train by executing phase-loop run-train --train <train-roadmap-file> --governed against your train roadmap Markdown file.

Frequently Asked Questions about claude-run-train

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

FAQPage Schema
How do I run a multi-repo release train with phase-loop?▼

Run phase-loop run-train --train <train-roadmap-file> to open draft PRs across all nodes in topological order. Add --governed to proceed through train-level review, sequential merge, and downstream re-verification.

What is the difference between phase-loop run and run-train?▼

phase-loop run is the per-repo phase loop and will not orchestrate a multi-repo train. run-train is the cross-repo coordinator that sequences draft PRs, review, and merges across all nodes in a train roadmap.

What format does a train roadmap file need?▼

The train roadmap is a Markdown file with a ## Nodes section listing ### Node: <repo> / <plan> entries. Each node includes **Depends on:** and **Channel:** fields that define the merge topology.

Can I resume a release train after a crash or failure?▼

Yes, the coordinator is crash-resumable. Re-invoke the same run-train command with --governed; the ledger skips already-merged nodes, re-verifies partially merged ones, and retries blocked nodes.

What happens when a downstream re-verify fails during merge?▼

The merge halts at the failed node, and that node plus its dependents are marked blocked. Already-merged upstream nodes stay merged under the forward-only guard; fix the integration issue and resume.