메뉴
Use before reporting a SpecRail PR as merge-ready. Collects read-only PR evidence, runs the offline PR gate, checks linked work, current head SHA, CI, review decision, review threads, merge state, and human merge authorization without merging.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | specrail-pr-gate |
| description | Use before reporting a SpecRail PR as merge-ready. Collects read-only PR evidence, runs the offline PR gate, checks linked work, current head SHA, CI, review decision, review threads, merge state, and human merge authorization without merging. |
Use this skill before saying a PR is merge-ready.
python3 checks/github_pr_evidence.py --github-repo <owner/repo> --pr <pr-number> --review-source independent_lane --json > <evidence.json>
python3 checks/pr_gate.py --repo . --evidence <evidence.json> --json
allowed: evidence satisfies the local merge-readiness policy.needs_human: deterministic evidence passed, but a human gate is missing.blocked: do not merge.The PR gate query must complete before any merge command, API call, or merge
lane is dispatched. Do not issue the GraphQL review-thread query, PR evidence
collection, pr_gate.py, and merge command in the same parallel tool batch or
parallel threads lane.
Required evidence:
gate_query_completed_at: when the current gate query finished.gate_query_head_sha: the head SHA observed by that gate query.review_source: independent_lane for a real reviewer/merge-reviewer lane,
or self_review when a lane failure was reported and self-review was
explicitly authorized.lane_failures: an array, empty when no reviewer lane failed.merge_dispatched_at and merge_head_sha when auditing a merge record after
dispatch.If review_source is self_review, evidence must include
self_review_authorization with actor, source, and scope from the current
conversation after the lane failure was reported. General queue-drain or merge
authorization does not satisfy this self-review exception.
GitHub exposes resolvedBy for review threads, but not the SpecRail lane role.
When resolved threads exist, pass lane-roster evidence through
--resolver-role-map so resolver logins can be mapped to resolver_role.
If the PR head changes, new review activity appears, CI changes, or merge is
deferred long enough that the evidence may be stale, collect fresh PR evidence
and rerun pr_gate.py before merging.
Use when turning an approved SpecRail product and technical spec into the numbered `tasks.md` plan. Creates stable task IDs, owners, done-when conditions, verification commands, dependencies, and handoff notes without implementing the tasks.
Use when writing or updating a SpecRail product spec for a linked issue. Produces the numbered `product.md` spec from the locale-appropriate template, focusing on user-facing behavior, goals, non-goals, and acceptance criteria without implementation detail.
Use when writing or updating a SpecRail technical spec for a linked issue. Produces the numbered `tech.md` spec from the locale-appropriate template, translating accepted product behavior into design, affected files, risks, verification, and rollback without starting implementation.
Use when the user says "implx", "use implx", "用 implx", or asks for the one-line SpecRail queue shortcut. Plain implx means drain the full actionable issue/PR queue in auto mode: run SpecRail preflight, create missing spec/task PR work before implementation, use threads for reviewer/merge-reviewer lanes when available, create per-issue implementation PRs, require CI/reviewThreads/pr_gate evidence, auto-merge on complete evidence, and perform closure audit. Say "implx review" / "implx 人工" for the review mode that keeps per-PR human merge authorization.
Use when implementing or draining a GitHub issue/PR queue in a SpecRail-governed repository where approved specs already exist, such as multiple numbered specs/GH packets that need one or more implementation PRs per issue. Maps issues to specs and existing PRs, supports full-queue drain requests from implx, selects single-agent or optional threads orchestration, preserves partial versus final closing semantics, and requires SpecRail verification plus PR gates before merge-readiness claims.
Use when performing an advisory SpecRail PR review. Checks linked issue/spec evidence, route gates, verification evidence, review-thread state, human-gate preservation, and implementation quality without granting final approval or merging.