review-pr

Reviews pull requests for architectural, security, and quality issues.

Updated May 10, 2026
One-click install
npx skills add https://github.com/VMRam95/vmram-skills --skill review-pr-vmram95
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/VMRam95/vmram-skills/tree/main/skills/review-pr
Command: npx skills add https://github.com/VMRam95/vmram-skills --skill review-pr-vmram95

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the inconsistency and time-sink of manual code reviews by providing an exhaustive, opinionated, and standardized checklist for every Pull Request.

Core Features & Use Cases

  • Strict Quality Control: Enforces architectural patterns, security best practices, and code quality standards automatically.
  • Comprehensive Analysis: Evaluates commit hygiene, cross-file consistency, and potential impact before merging.
  • Use Case: Use this skill to block merges that contain hardcoded secrets, debug logs, or architectural regressions, ensuring only high-quality code reaches your main branch.

Quick Start

Invoke the review-pr skill to perform a full audit of the current pull request.

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 code reviews to enforce strict merge criteria?

Automate pull request code reviews by using an opinionated analysis tool to check git diffs, commit history, and PR metadata against architectural and security standards, ensuring codebase integrity before merging.

Can I use the GitHub CLI to gather context for automated code review?

Yes, automated code review can optionally integrate with the GitHub CLI to gather PR context and validate changes against established project standards for a comprehensive audit.

What security vulnerabilities can an automated code review catch in a git diff?

Automated code review scans git diffs to block merges containing hardcoded secrets, debug logs, and security vulnerabilities, enforcing strict quality control against established best practices.

Does automated code review analyze commit history and cross-file consistency?

Yes, automated code review performs a comprehensive analysis evaluating commit hygiene, cross-file consistency, and potential impact to identify architectural flaws and quality issues.

What's the best way to block merges that contain hardcoded secrets or debug logs?

The best way to block problematic merges is to use an exhaustive, opinionated code review checklist that automatically enforces security best practices and code quality standards on every pull request.

When do I need an opinionated code review checklist for my pull requests?

You need an opinionated code review checklist when manual reviews become inconsistent and time-consuming, requiring standardized enforcement of architectural patterns and security best practices.