pr-review-format

Enforce evidence-based verification and structured formatting for pull request reviews.

45|7|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/richkuo/rk-skills --skill pr-review-format
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review-format
Source: https://github.com/richkuo/rk-skills/tree/main/skills/pr-review-format
Command: npx skills add https://github.com/richkuo/rk-skills --skill pr-review-format

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates inconsistent, shallow, or biased pull request reviews by enforcing a rigorous, evidence-based verification methodology that ensures every finding is substantiated and actionable.

Core Features & Use Cases

  • Verification Enforcement: Mandates independent sourcing of facts and full file analysis before any review comment is written.
  • Structured Disposition: Categorizes feedback into clear sections like Needs Fixing, Recommended Optional, and Requires Human Review to prevent ambiguity.
  • Use Case: Use this skill when you need to perform a high-stakes code review on a critical security patch or complex architectural change to ensure no edge cases or safety risks are overlooked.

Quick Start

Load the pr-review-format skill before you begin analyzing the pull request to ensure your review follows the required verification and formatting rules.

Frequently Asked Questions about pr-review-format

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize pull request reviews for consistent quality?

Standardize pull request reviews by applying a structured, evidence-based protocol that mandates independent fact sourcing and full file analysis before writing feedback, ensuring consistent quality. This prevents shallow or biased reviews by enforcing rigorous verification.

What is the best way to format code review feedback to prevent ambiguity?

Format code review feedback by categorizing comments into clear dispositions like Needs Fixing, Recommended Optional, and Requires Human Review. This structured formatting prevents ambiguity and ensures every finding is substantiated and actionable.

How do I conduct a high-stakes code review on a critical security patch?

Conduct a high-stakes code review on a critical security patch by enforcing a rigorous, evidence-based verification methodology. This ensures every finding is substantiated and actionable, preventing edge cases or safety risks from being overlooked.

When do I need an evidence-based verification methodology for code analysis?

You need an evidence-based verification methodology for code analysis when performing high-stakes reviews on critical security patches or complex architectural changes. This ensures safety-critical verification and clear communication of findings without bias.

How do I enforce materiality filtering and attribution standards in software engineering workflows?

Enforce materiality filtering and attribution standards in software engineering workflows by adhering to specific sectioning rules during pull request reviews. This ensures high-integrity code analysis and consistent, actionable feedback across the team.

Why does my pull request review lack consistent and actionable feedback?

Your pull request review lacks actionable feedback due to inconsistent, shallow, or biased analysis. Eliminate this by enforcing a rigorous, evidence-based verification methodology that requires full file analysis and independent fact sourcing before commenting.