pr-review
Standardized guidelines and templates for structuring Pull Request reviews so feedback is actionable, encouraging, and extractable by the Native Edge Graph. MANDATORY ROI WARNING: Skipping the review template guarantees CI lint failure. Triggers: Reviewing a PR (yours or peer's) — structured eval metrics, graph ingestion tags, severity ladder, restates §0 merge gate, post-comment A2A commentId hand-off (reviewer→author) per guide §10, Evidence Audit + Source-of-Authority sections (template §) for substrate/runtime-AC PRs and authority-citation review-comments.
72
88%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
PR Review Skill
If you are tasked with conducting a Pull Request review, generating feedback, or helping a user formulate a PR Review, you MUST immediately use the view_file tool to read and strictly adhere to .agents/skills/pr-review/references/pr-review-guide.md before proceeding.
Prior-art sweep gate (PR-review = the last line of defense, per AGENTS.md §verify_before_assert): before scoring, run a cheap 3–10-call query_raw_memories / query_summaries sweep of the PR's decision space — a prior session may have settled the shape, an ADR may already govern it, or the same wrong-shape may have been caught before. The sweep RESULT is the V-B-A; CI-green ≠ AC-met (#13354).
Templates: Cycle 1: load pr-review-template.md (full structure). Cycle N (≥2): load pr-review-followup-template.md (compact delta). Budgeted closure: at RC2 or >24KB load audits/review-cost-circuit-breaker.md; after RC2 use COMMENTED closure, approval/polish, guarded A+FU, or one complete terminal D+S—never another ordinary RC.
- Repository
- neomjs/neo
- Commit
b4a1b58
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.