opencode-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 opencode-run-train-consiliency
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: opencode-run-train
Source: https://github.com/Consiliency/agent-harness/tree/main/skills-src/opencode/opencode-run-train
Command: npx skills add https://github.com/Consiliency/agent-harness --skill opencode-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 OpenCode entry point to the phase-loop run-train coordinator, which automates that entire cross-repo release flow. ## Core Features & Use Cases - Topo-ordered draft PRs: Opens draft pull requests 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 before merging it. - Crash-resumable ledger: Inspects and resumes state via phase-loop train-status, skipping merged nodes, re-verifying partially merged ones, and retrying blocked nodes. - Use Case: A platform team shipping a breaking API change across five service repos defines a train roadmap with Nodes, Depends on, and Channel fields, then runs the coordinator to open all draft PRs, gather train-level review, and merge 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 opencode-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 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 merge ordering and release channels.

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. Use --ledger to specify an explicit ledger path.

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 the run.

Why should I not run phase-loop run on a train roadmap file?▼

phase-loop run is the per-repo loop and will not orchestrate a multi-repo train. Only phase-loop run-train understands the Nodes, Depends on, and Channel structure needed for cross-repo sequencing.