pr-review-common-patterns

Analyze pull requests to identify common review patterns and issues.

Updated Sep 8, 2025
One-click install
npx skills add https://github.com/randalmurphal/claude-config --skill pr-review-common-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review-common-patterns
Source: https://github.com/randalmurphal/claude-config/tree/main/skills/pr-review-common-patterns
Command: npx skills add https://github.com/randalmurphal/claude-config --skill pr-review-common-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill equips reviewers with a catalog of common patterns found in pull requests, including false positives, critical security vulnerabilities, performance issues, and breaking changes. It helps reviewers quickly identify recurring problems, improve the accuracy of their feedback, and avoid flagging non-issues, leading to more efficient and effective code reviews.

Core Features & Use Cases

  • False Positive Detection: Learn to identify and avoid flagging issues already handled by calling code, error handlers, or type hints.
  • Security Vulnerability Identification: Recognize critical patterns like SQL injection, auth bypass, hardcoded secrets, and PII in logs.
  • Performance Bottleneck Recognition: Spot N+1 queries, algorithmic regressions, and missing caching that degrade application speed.
  • Use Case: As an AI agent reviewing a pull request, use this skill to cross-reference potential findings against known false positive patterns before reporting, ensuring only valid and impactful issues are flagged.

Quick Start

Use the pr-review-common-patterns skill to check if the reported "missing validation" is a false positive due to validation in the caller.

Frequently Asked Questions about pr-review-common-patterns

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

FAQPage Schema
How do I avoid false positives when reviewing pull requests?

False positives occur when code already handles validation, errors, or type safety upstream. Check if the caller validates input, error handlers catch edge cases, or type hints prevent issues before flagging them as problems in the PR.

What security vulnerabilities should I look for in code reviews?

Common PR security issues include SQL injection, authentication bypass, hardcoded secrets, and personally identifiable information in logs. Recognizing these patterns helps you catch critical vulnerabilities before they reach production.

How can I spot performance issues in pull requests?

Performance bottlenecks in PRs include N+1 queries, algorithmic regressions, and missing caching layers. Identifying these patterns early prevents degradation of application speed and user experience.

What counts as a breaking change in a pull request?

Breaking changes alter APIs, remove functionality, or modify contracts in ways that require downstream updates. Recognizing these patterns during review prevents unexpected failures in dependent code.

How do I improve code review accuracy across different languages and repositories?

Use a catalog of common review patterns applicable across languages and codebases. Cross-referencing potential findings against known issues ensures only valid, impactful problems are reported.