Note: The original developer is the forge-harness original developer (development source + meta-monitoring home). In external user install environments, the install environment user themselves is the baseline integrity gate operator (following path B generalization baseline / SKILL_detail.md §External User Environment Adaptation Path §).

harness-pr-reviewer — Hub Gate Operation Rule Automation

When a PR is submitted, checks consistency against the user environment's baseline assets (CLAUDE.md · memory · naming · asset classification) and attaches a review comment. 5-step: diff read → 8-matrix check → self-catch → comment attachment → merge recommendation.

Activation Triggers

Renamed from hub-cc-pr-reviewer (2026-09-12, operator decision). The old name said where it was born (the hub's own cc reviewing its own PRs). What it actually is — measured on qasp/pmh PRs in 2026-09 — is the standalone doorway through which a field harness verifies its own submitted PR with FH's review capability. Old-name utterances ("hub-cc-pr-reviewer", "hub review", "hub cc review") still route here; downstream forks that carry the old directory name (PMH) keep working until they sync. No redirect stub directory is shipped (same policy as phantom-quench).

PR #N input: "Review PR #N" / "Check PR #N" / "hub review" (old-name alias) / "harness PR review" / "baseline consistency check"
Action leader cc → hub sync point: Large decision area PR catch (following Option C Hybrid policy — memory creation / CLAUDE.md change / CATALOG round / skill v0.x evolution / policy change / asset synergy branch judgment)
Hub cc session entry: Layer A auto-read recent external commit catch (auto-discover new PRs)