pr-review-standards

Name: pr-review-standards
Availability: InStock
Author: randalmurphal

Enforce evidence-based PR review standards for code analysis and verification.

Updated Sep 8, 2025

Search Tags:#logging #evidence #type-hints #code-review #pr-review

Ready to run

npx skills add https://github.com/randalmurphal/claude-config --skill pr-review-standards

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-review-standards
Source: https://github.com/randalmurphal/claude-config/tree/main/skills/pr-review-standards
Command: npx skills add https://github.com/randalmurphal/claude-config --skill pr-review-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code quality standards for PR review agents including try/except rules, logging patterns, type hints, and verification requirements. Use when reviewing code changes, spawning PR review agents, or validating code quality.

Core Features & Use Cases

NO Assumptions: Flag uncertain findings as needs_verification.
PROOF Required: Require evidence (snippets, traces, tests).
Contextual Review: Review entire function with context.

Quick Start

Apply PR review standards to generate structured, evidence-backed reviews for code changes.

Frequently Asked Questions about pr-review-standards

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

FAQPage Schema

How do I conduct evidence-based code reviews for pull requests?▼

Evidence-based PR reviews require proof-backed findings with code snippets, test results, or traces rather than assumptions. This standard enforces structured verification, type hints, logging hygiene, and contextual assessment to produce traceable, non-ambiguous review summaries aligned with severity levels.

What makes a pull request review verifiable and reproducible?▼

Verifiable PR reviews flag uncertain findings as needs_verification, require concrete evidence for each claim, review functions with full context, and enforce consistent logging patterns and type hints. This creates auditable trails and prevents ambiguous or assumption-based feedback.

How do I apply code quality standards consistently across PR reviews?▼

Apply standardized PR review patterns by codifying quality rules for security, performance, tests, and code analysis, then enforce try/except patterns, logging standards, and type hints during review. This ensures disciplined, repeatable assessment across all pull request validation workflows.

Can I use these PR review standards with automated code analysis tools?▼

Yes, these standards apply when spawning PR review agents or validating code across code-analysis, security, performance, and verification workflows. They satisfy functional requirements for structured validation and traceable evidence collection in both manual and automated review contexts.

What should I do when I'm unsure about a code quality finding in a PR?▼

Flag uncertain findings as needs_verification rather than making assumptions. Provide evidence requirements—code snippets, test traces, or specific context—so reviewers can complete verification before approving or requesting changes.