gemini-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 gemini-run-train-consiliency
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gemini-run-train
Source: https://github.com/Consiliency/agent-harness/tree/main/skills-src/gemini/gemini-run-train
Command: npx skills add https://github.com/Consiliency/agent-harness --skill gemini-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 Gemini CLI 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 --governed, 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 and dependencies, run the coordinator to open all draft PRs, then pass --governed to review and merge them sequentially with downstream re-verification. ## Quick Start Ask the assistant to run the release train by invoking phase-loop run-train with your train roadmap file, adding the governed flag when you are ready to review and merge.

Frequently Asked Questions about gemini-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 <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 run-train and run in phase-loop?▼

run-train orchestrates a multi-repo train roadmap with cross-node dependencies, while run executes the per-repo phase loop. Invoking run on a train roadmap file will not coordinate the train.

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

Yes, the coordinator is crash-resumable via its ledger. Re-invoke the same command with --governed; already-merged nodes are skipped, downstream nodes are re-verified, and blocked nodes are retried.

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

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

How do I check release train status without changing state?▼

Run phase-loop train-status --train <file> to inspect the ledger. It reports statuses such as drafts_open, review_halted, merge_halted, or merge_failed without modifying any state.