skills.rest
BrunoAlpezdev
BrunoAlpezdevCOMMUNITY
Explore all skills by this author →
GitHub

review-pr

Review pull request diffs with severity-scored file and line-level fix suggestions.

Updated Apr 11, 2026
Search Tags:#code review#pull request#GitHub CLI#severity scoring#security checks#Supabase conventions#shadcn/ui rules
One-click install
npx skills add https://github.com/BrunoAlpezdev/lluvia-de-ideas --skill review-pr-brunoalpezdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/BrunoAlpezdev/lluvia-de-ideas/tree/main/.claude/skills/review-pr
Command: npx skills add https://github.com/BrunoAlpezdev/lluvia-de-ideas --skill review-pr-brunoalpezdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the risk of merging low-quality, buggy, insecure, or inconsistent code by performing structured PR reviews against your project’s conventions and safety rules.

Core Features & Use Cases

  • Diff-first review workflow: Pulls the PR diff and reviews the full contents of every changed file to preserve necessary context.
  • Standards-focused checklist: Evaluates correctness, architecture boundaries, conventions, Supabase usage rules, shadcn/ui constraints, and security requirements.
  • Severity-based reporting: Scores each finding and reports only issues at or above a defined severity threshold to avoid review noise.
  • Use cases: Ideal for teams that want repeatable PR quality control, consistent enforcement of component/import boundaries, and disciplined backend/frontend Supabase patterns.

Quick Start

Tell the AI to review your pull request by saying: review PR #123.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I automate code review for GitHub pull requests to enforce conventions?▼

Automated code review evaluates PR diffs against conventions, architecture boundaries, and security rules. It analyzes full changed file contents to provide severity-scored, actionable feedback with file and line-level fix suggestions.

How does severity scoring work in PR code reviews to suppress low-value noise?▼

Severity scoring filters review noise by assigning a score to each finding. It reports only issues at or above a configured severity threshold, ensuring reviewers receive actionable, high-priority feedback instead of minor style suggestions.

Can I use this to check Supabase integration rules and shadcn/ui constraints in a PR diff?▼

Yes, PR review checks Supabase integration rules and shadcn/ui constraints. It evaluates backend/frontend patterns and component/import boundaries across the changed files to ensure disciplined usage before merge.

What is the best way to review a pull request diff for security risks and architecture boundaries?▼

The best way is a diff-first review that pulls the PR diff and analyzes full changed file contents. This preserves context to accurately evaluate security risks, correctness, and architecture boundaries.

Do I need GitHub CLI to review pull requests for code quality?▼

GitHub CLI is used to pull PR diffs for code quality review workflows. The review process requires the diff data to evaluate correctness, conventions, and security risks with severity-scored feedback.

Related Skills

Explore More Software Engineering Skills→
SandAI-orgSandAI-org
325

code-review

Inspect ahead-of-base diffs and generate structured P0-P4 markdown review reports.

Official
Intermediate
comeritocomerito

code-review

Identify changed files in a pull request and assess them against architecture, security, and quality rules.

Official
Advanced
KartikSharma4448KartikSharma4448

fullstack-js

Standardize full-stack JavaScript architecture with TypeScript, Zod, wouter, and shadcn.

Community
Advanced
Rune-kitRune-kit
82

sast

Run static analysis tools and normalize findings into unified severity levels.

Official
Advanced