메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | specrail-review-pr |
| description | 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. |
Use this skill for the review_pr route.
python3 checks/route_gate.py --repo . --route review_pr --issue <issue-number> --pr <pr-number> --state impl_pr_open --json
## Summary and
## Verdict, keep inline comments bound to real diff path / line /
side values, and only add start_line / start_side together for an
inclusive diff range. Suggested changes must be non-empty and appear only on
RIGHT-side comments, either through a suggestion field, a fenced
suggestion block, or both.python3 checks/review_json_gate.py --repo . --review artifacts/review/pr-<pr-number>.json --diff <patch> --json
skills/specrail-pr-gate/SKILL.md.Record review_round and review_mode in the review result JSON:
full: the whole PR is reviewed. Allowed for rounds 1-2. A full review
past round 2 requires a quoted human_full_review_request; otherwise
checks/review_json_gate.py blocks it.resumed: the same reviewer lane continues with its prior context and
re-checks its earlier findings.diff_only: a fresh pass over only the changes since base_head_sha
(the head reviewed in the prior round; required field).resumed and diff_only rounds require review_round >= 2 and a
prior_findings[] checklist where every prior finding carries a status
(resolved | unresolved | obsolete). Record pr and head_sha as the
grouping key so rounds for the same PR can be ordered.
Reviewer lanes may resolve review threads only after re-checking that the finding is fixed or no longer applies. A reviewer lane may resolve its own thread, a successor reviewer lane may resolve after re-review, and a human maintainer may resolve directly.
Implementation lanes and orchestrators must not call resolveReviewThread for
reviewer-lane findings. They may reply with context and push fixes, but the
resolution action stays with the reviewer or human.
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 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.