review-pr

Review pull request changes and report bugs, vulnerabilities, and merge verdicts.

114|31|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/SeifBenayed/cloclo --skill review-pr-seifbenayed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/SeifBenayed/cloclo/tree/main/.claude/skills/review-pr
Command: npx skills add https://github.com/SeifBenayed/cloclo --skill review-pr-seifbenayed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually reviewing pull requests is time-consuming and often misses critical bugs, security vulnerabilities, performance bottlenecks, and code quality issues that can cause production outages or security breaches if merged unchecked.

Core Features & Use Cases

  • Comprehensive Issue Detection: Scans changed code for logic errors, null/undefined access, race conditions, injection flaws, XSS vulnerabilities, hardcoded secrets, N+1 queries, missing error handling, style inconsistencies, and gaps in test coverage.
  • Structured Review Output: Delivers a clear summary of changes, a prioritized list of required fixes, non-blocking improvement suggestions, and a final merge verdict (Approve / Request Changes / Needs Discussion) with exact file paths and line numbers for all findings.
  • Use Case Example: When a developer submits a PR adding a new payment processing endpoint, this skill will flag missing input validation, hardcoded API keys, unhandled payment failure edge cases, and missing unit tests for invalid transaction amounts.

Quick Start

Use the review-pr skill to analyze all changes in your current open pull request against the base branch and receive a structured review with actionable feedback and a merge recommendation.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I automate pull request reviews to catch bugs and security flaws before merging?

Automated PR review scans changed code against a base branch to identify logic errors, injection flaws, hardcoded secrets, and missing tests before merge. It delivers a structured report with required fixes, non-blocking suggestions, and a final merge verdict.

What issues can a pre-merge code review automatically detect in my feature branch?

Pre-merge code review detects null access, race conditions, XSS vulnerabilities, hardcoded secrets, N+1 queries, missing error handling, and test coverage gaps. It analyzes changes from any feature branch against a base branch like main.

Does automated PR review work with any programming language and Git workflow?

Automated PR review supports codebase changes from any language or framework within Git-based software development workflows. It reviews changes from any feature branch against a base branch like main or master.

How do I get a merge verification verdict with specific file and line numbers for my PR?

Merge verification provides a final verdict of Approve, Request Changes, or Needs Discussion alongside a summary of changes. All findings include specific file paths and line numbers to pinpoint required fixes and non-blocking suggestions.

What is the best way to flag missing input validation and unhandled edge cases in a new API endpoint?

The best way to flag missing input validation and unhandled edge cases is automated PR review, which identifies logic errors, missing error handling, and security vulnerabilities before code is merged into the main branch.

What are the limitations of automated code review for finding performance bottlenecks?

Automated code review identifies performance bottlenecks like N+1 queries alongside security vulnerabilities and quality gaps, but requires a Git branch structure to process changes and does not replace manual architectural discussion for complex designs.