Menu
Present an evidence-grounded pull request closeout decision after review, CI, or real-machine validation.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle 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.
Create and revise a structured topic outline from an evolving brief, audience, angle, thesis, sections, questions, and sources.
Create or replace a complete semantic release-notes snapshot.
| name | pr-closeout |
| description | Present an evidence-grounded pull request closeout decision after review, CI, or real-machine validation. |
Use this capability when the user asks whether a pull request is ready, requests a review summary, or needs validation evidence consolidated before merge.
Call the current Tool catalog entry for com.homerail.pr-closeout:upsert_pr_closeout using the harness-safe wire name supplied by the current turn. Reuse one stable plugin-owned id, such as com.homerail.pr-closeout:owner-repo-pr-21, so later evidence replaces the same report.
Send a complete snapshot on every call. Include only checks, blockers, review threads, platform results, and evidence verified in the current session or explicitly supplied by the user. Use unknown, pending, or an empty list when evidence is unavailable. Never infer a passing platform from another platform and never convert a skipped check into a pass.
Set recommendation as follows:
ready: every required gate has direct passing evidence and no unresolved blocker remains.blocked: at least one required gate is pending, running, unavailable, or failed.changes_requested: a verified defect requires code changes.unknown: the available evidence cannot support a decision.Model the verification flow with stable node ids and explicit depends_on edges. A flow node status must reflect the evidence, not the intended plan. Put source URLs only when they are known and safe; never invent a PR, check, review, or artifact URL.
This Tool projects data only. It does not approve or merge a pull request, rerun CI, resolve review threads, or modify GitHub state. Do not describe a navigation link as if its external action already happened.
Use the matching PR closeout Tool only when it is listed for the current turn. Do not substitute a legacy dynamic widget. If the report is not placed on the canvas, tell the user only that visible result and offer to retry.