メニュー
Determine whether a GitHub pull request can leave Draft or is ready for its owner to merge, using immutable validation, review, CI, dependency, and approval evidence. Never merge a pull request.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Design and maintain truthful HomeRail generative UI for voice or text. Use for dashboards, cards, charts, visual reports, screenshot-ready output, or supervised multi-Actor live panels that update in parallel and across follow-ups.
Exact HomeRail local-source TypeScript CLI command and configuration reference. Use when: (1) configuring or invoking the homerail CLI from a local checkout, (2) listing orchestration templates, starting runs, checking status, (3) supervising DAG runs, inspecting chats/handoffs/scorecards, (4) injecting instructions or replaying runs, or (5) translating a known HomeRail operation into an exact hr command. For workflow topology selection use homerail-dag-patterns; for multi-Actor Surface lifecycle and operational procedure use homerail-dag-ops. For deployment, service startup, or skill installation, use homerail-install-ops first.
Run, monitor, inspect, debug, and author HomeRail DAG workflows through the CLI or Manager Tools, including supervised multi-Actor runs with stable live Surfaces and later per-Actor follow-ups. Use when: (1) listing templates, (2) starting a DAG run, (3) supervising or watching a run, (4) inspecting chats, handoffs, scorecard, eval-run, or replay output, (5) creating multiple parallel UI panels that update while Actors work, (6) sending commands to waiting Actors, (7) injecting instructions into running nodes, or (8) creating custom DAG templates. For installing or starting Manager/Node/Worker services, use homerail-install-ops first.
Select, inspect, instantiate, adapt, and validate HomeRail's built-in DAG design patterns. Use when an agent needs to design a reusable workflow for periodic triage, read-only issue diagnosis, planner/worker fan-out, on-demand executor/advisor consultation, budget admission, graduated trust, standing-goal verification, quorum decisions, adversarial builder/breaker review, monotonic improvement, or evidence-driven process evolution. Also use when deciding whether a workflow needs condition, loop, join, or while gateway semantics. Patterns describe control-flow invariants; for stable live Actor panels, Surface updates, or follow-up commands, use homerail-dag-ops and a concrete presentation-aware Workflow.
Present an evidence-grounded pull request closeout decision after review, CI, or real-machine validation.
Create and revise a structured topic outline from an evolving brief, audience, angle, thesis, sections, questions, and sources.
| name | homerail-pr-closeout |
| description | Determine whether a GitHub pull request can leave Draft or is ready for its owner to merge, using immutable validation, review, CI, dependency, and approval evidence. Never merge a pull request. |
Use the concrete pr-closeout orchestration after implementation and local
validation are complete. Do not substitute a conversational checklist.
gh pr merge.For a Draft PR, use one of these paths:
run_pr_closeout with repo, integer pr, phase: draft, and durable
validation_runs. Do not invent run ids.hr dag run-template pr-closeout with explicit operator-attested local
evidence bound to a commit SHA.A successful result means only ready_for_review; the PR must still run normal
GitHub CI and PR Review after leaving Draft.
For a non-Draft PR, call run_pr_closeout with durable validation_runs,
especially the matching HomeRail PR Review run. Do not use generic
create_and_run, shell, gh, or curl to reconstruct the snapshot. The
workflow may pause at merge_approval. Return the real run id and the exact
blocker list or pending approval hash. Only human:owner may decide that
approval, and the user still merges manually.
After a terminal decision, consume the declared pr-closeout.json artifact
with hr dag artifact <run-id> pr-closeout.json --output pr-closeout.json.
Never reconstruct closeout evidence by scraping handoffs.
Read docs/scenarios/pr-closeout.md for the full evidence contract.