How do I install the Homerail Pr Review skill?

Run npx skillmds@latest add xiaotianfotos/homerail-pr-review in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Homerail Pr Review safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Homerail Pr Review?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Homerail Pr Review free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Homerail Pr Review?

xiaotianfotos (@xiaotianfotos) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Homerail Pr Review by xiaotianfotos

Name: Homerail Pr Review
Author: xiaotianfotos

Homerail Pr Review

Run HomeRail's built-in read-only pull request review DAG. Use when the user asks to review a GitHub PR, requests an evidence-backed PR audit, or wants a reusable independent Qwen, Kimi, and GLM review with retained findings.

xiaotianfotos Updated Sep 17, 2026

File contents

HomeRail PR Review

Use the concrete pr-review orchestration. Do not generate a replacement DAG and do not substitute a single-agent review.

Manager Agent Path

When the user says 审查 PR #25, review PR 25, or equivalent:

Resolve the repository from the current project or ask only when no repository is available.
Call run_pr_review with only repo in owner/name form and integer pr. This tool resolves immutable .base.sha and .head.sha plus trusted base and head clone URLs in code. Never copy, infer, reverse, or manually substitute those fields. Do not use gh, curl, instantiate_dag_pattern, or generic create_and_run when this tool exists.
Return the real run id immediately and use get_run_status for progress.
On completion, report the final published handoff and artifact paths. Never claim findings that are not present in the DAG evidence.

The workflow is read-only. It must never create a commit, approve a GitHub PR, submit a GitHub review, or merge anything. Its internal Quorum is evidence validation, not GitHub approval.

CLI Path

hr dag run-template pr-review \
  --input '{"repo":"xiaotianfotos/homerail","pr":25}'

The CLI resolves trusted GitHub metadata, preserves explicitly pinned SHAs, validates the final input contract, syncs the tracked Asset, and starts the run. Clone URLs always come from GitHub metadata, never logical input. Add --wait for CI or unattended operation, then retrieve fixed outputs with:

hr dag artifacts <run-id>
hr dag artifact <run-id> pr-review.json --output pr-review.json
hr dag artifact <run-id> pr-review.md --output pr-review.md

Evidence Contract

A useful run contains:

three complete reviewer handoffs from Qwen, Kimi, and GLM;
a deduplicated report that preserves every complete reviewer finding;
three independent approve/request-changes/abstain votes;
a deterministic gate requiring two approvals and zero retained findings;
declared pr-review.json and pr-review.md artifacts;
Manager audit and metrics records for the run.

Treat a cancelled run with a published report as inconclusive, not as a clean review. Infrastructure, contract, or artifact failures are errors and must not be rendered as zero findings. Do not reconstruct a report by scraping raw handoffs; consume only the Manager-validated declared artifacts.

---name: homerail-pr-reviewdescription: Run HomeRail's built-in read-only pull request review DAG. Use when the user asks to review a GitHub PR, requests an evidence-backed PR audit, or wants a reusable independent Qwen, Kimi, and GLM review with retained findings.---# HomeRail PR ReviewUse the concrete `pr-review` orchestration. Do not generate a replacement DAGand do not substitute a single-agent review.## Manager Agent PathWhen the user says `审查 PR #25`, `review PR 25`, or equivalent:1. Resolve the repository from the current project or ask only when no repository is available.2. Call `run_pr_review` with only `repo` in `owner/name` form and integer `pr`. This tool resolves immutable `.base.sha` and `.head.sha` plus trusted base and head clone URLs in code. Never copy, infer, reverse, or manually substitute those fields. Do not use `gh`, `curl`, `instantiate_dag_pattern`, or generic `create_and_run` when this tool exists.3. Return the real run id immediately and use `get_run_status` for progress.4. On completion, report the final published handoff and artifact paths. Never claim findings that are not present in the DAG evidence.The workflow is read-only. It must never create a commit, approve a GitHub PR,submit a GitHub review, or merge anything. Its internal Quorum is evidencevalidation, not GitHub approval.## CLI Path```bashhr dag run-template pr-review \ --input '{"repo":"xiaotianfotos/homerail","pr":25}'```The CLI resolves trusted GitHub metadata, preserves explicitly pinned SHAs,validates the final input contract, syncs the tracked Asset, and starts the run.Clone URLs always come from GitHub metadata, never logical input. Add `--wait`for CI or unattended operation, then retrieve fixed outputs with:```bashhr dag artifacts <run-id>hr dag artifact <run-id> pr-review.json --output pr-review.jsonhr dag artifact <run-id> pr-review.md --output pr-review.md```## Evidence ContractA useful run contains:- three complete reviewer handoffs from Qwen, Kimi, and GLM;- a deduplicated report that preserves every complete reviewer finding;- three independent approve/request-changes/abstain votes;- a deterministic gate requiring two approvals and zero retained findings;- declared `pr-review.json` and `pr-review.md` artifacts;- Manager audit and metrics records for the run.Treat a cancelled run with a published report as `inconclusive`, not as a cleanreview. Infrastructure, contract, or artifact failures are errors and must notbe rendered as zero findings. Do not reconstruct a report by scraping rawhandoffs; consume only the Manager-validated declared artifacts.

Frequently asked questions