pr-review-guidelines

Classify pull request feedback into BLOCKER, WARNING, or NIT with confidence scoring.

Updated Feb 4, 2026

Search Tags:#checklist #blockers #review #confidence #code-review #rubrics #nit

Ready to run

npx skills add https://github.com/SuperCorks/agent-skills --skill pr-review-guidelines

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-review-guidelines
Source: https://github.com/SuperCorks/agent-skills/tree/main/pr-review-guidelines
Command: npx skills add https://github.com/SuperCorks/agent-skills --skill pr-review-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides structured rubrics and standards to guide developers through high-quality code reviews, ensuring consistent feedback and faster critique loops.

Core Features & Use Cases

Clear rubric for BLOCKER, WARNING, and NIT classifications.
Confidence scoring (0-100) and a reusable review checklist.
Generates a structured feedback report to speed up code reviews and onboarding for new engineers.

Quick Start

Use the pr-review-guidelines skill to guide a PR review by applying the rubric and generating a categorized feedback report.

Frequently Asked Questions about pr-review-guidelines

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

FAQPage Schema

How do I structure a code review with clear rubrics?▼

Structure a code review by applying standardized rubrics that classify feedback into BLOCKER, WARNING, or NIT categories, adding confidence scoring and a checklist to generate a deterministic, actionable feedback report.

What is the difference between a blocker and a nit in code review?▼

A blocker in code review indicates a critical issue that must be fixed before merging, while a nit represents a minor stylistic or preferential note, with warnings falling between these two extremes in the structured rubric.

How do I standardize pull request feedback across my software projects?▼

Standardize pull request feedback by applying a fixed set of requirements including clear frontmatter metadata, sections for problem and features, and a categorized feedback report to ensure consistent critique loops.

Can I use a confidence score to improve my code review checklist?▼

Use a confidence score from 0-100 alongside a reusable review checklist to quantify review certainty, ensuring high-quality code reviews and faster onboarding for new engineers across software projects.

What's the best way to speed up code reviews for new engineers?▼

Speed up code reviews for new engineers by generating a structured feedback report that applies clear rubrics, enabling faster critique loops and consistent feedback across all software project pull requests.