silo-runtime-handoff

Writes runtime URLs, E2E steps, and handoff comments on silo pull requests.

1|Updated Jul 3, 2026
One-click install
npx skills add https://github.com/Ryokuman/new_human_ochestrator --skill silo-runtime-handoff-ryokuman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: silo-runtime-handoff
Source: https://github.com/Ryokuman/new_human_ochestrator/tree/main/system/20-skills/silo-runtime-handoff
Command: npx skills add https://github.com/Ryokuman/new_human_ochestrator --skill silo-runtime-handoff-ryokuman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a silo PR passes the Codex review loop (or skips it when Codex review is not configured), reviewers still need to know how to actually run and verify the change. This Skill prepares the runtime environment, checks server health, and posts a structured Korean PR comment with server addresses, E2E verification steps, and any execution blockers before calling the user for re-review. ## Core Features & Use Cases - Runtime preparation: Starts only the runtimes declared in the resolved runtime_set (Docker DB, shared BE/API, vite-harness or FE dev server) and verifies them via health checks from shared-runtime-registry.yaml. - Config-based branching: Distinguishes between a runnable handoff, a partial-failure handoff with fallback evidence, and a config-missing handoff requiring add-shared-runtime or project runtime_set definitions. - Structured PR comment: Posts a Korean handoff comment containing head SHA, Codex review evidence, running server table, E2E steps, test inputs, expected results, and an execution-blocked items table. - Use Case: A task silo PR modifying TypeScript product code passes codex-review pass; the Skill boots the Docker DB and shared BE/API, confirms health checks, and comments the exact URL and click-by-click E2E procedure so the user can re-review immediately. ## Quick Start After the silo PR passes Codex review, run the silo runtime handoff to start the required runtimes and post the E2E verification comment on the PR.

Frequently Asked Questions about silo-runtime-handoff

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

FAQPage Schema
How do I hand off a silo PR for user re-review after Codex review passes?

Run the silo runtime handoff once the PR head shows codex-review pass or a recorded Codex-review-not-configured fallback. It starts the required runtimes, verifies health checks, and posts a Korean PR comment with server URLs and E2E steps.

What is a runtime_set and how is it resolved?

A runtime_set groups the servers a task needs, such as Docker DB, shared BE/API, and vite-harness. It is resolved in priority order from run_set.required_runtime_set, task.runtime_set, qa_or_runbook.runtime_set, then project.common_runtime_set.

When should the silo runtime handoff not run?

It must not run before codex-review pass on PRs with Codex review enabled, or on PRs that only change docs, skills, project SSoT, config examples, or PR templates. It also never merges the PR itself.

What happens if a required runtime fails its health check?

The handoff does not mark E2E as available. The PR comment lists the failed runtime, the failing command or URL, fallback evidence, and remaining manual checks instead of masking the failure.

What if no runtime_set is defined for the silo?

The Skill reports a config-missing handoff rather than guessing a server setup. The PR comment notes the missing runtime_set definition and that add-shared-runtime or project SSoT updates are needed.