code-review-patterns

Generate structured code review feedback with evidence and severity guidelines.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide to effective code reviews, ensuring high-quality code, fostering collaboration, and streamlining the review process. It helps reviewers provide actionable, evidence-based feedback and authors respond constructively, reducing friction and improving code quality.

Core Features & Use Cases

  • Structured Review Workflow: Follows a clear process from automated checks to detailed code, test, and documentation review.
  • Constructive Feedback Templates: Provides a formula (OBSERVATION + EVIDENCE + IMPACT + SUGGESTION) and templates for clear, actionable feedback.
  • Code Smells & Severity Guidelines: Identifies critical issues (SQL injection, auth bypass) and helps assign appropriate severity levels.
  • Use Case: As an AI agent, use this skill to systematically review a pull request, identify potential security vulnerabilities, suggest specific fixes with code examples, and provide a summary of findings based on established best practices.

Quick Start

Use the code-review-patterns skill to generate a detailed review checklist for a pull request, focusing on security and performance.

Frequently Asked Questions about code-review-patterns

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

FAQPage Schema
How do I structure actionable feedback during code reviews?

Actionable feedback follows the OBSERVATION + EVIDENCE + IMPACT + SUGGESTION formula. This approach ensures reviewers identify specific issues with supporting context, explain consequences, and propose concrete fixes—reducing ambiguity and enabling authors to respond constructively.

What security vulnerabilities should I prioritize when reviewing pull requests?

Prioritize critical security issues like SQL injection and authentication bypass. Code-review patterns guide you to identify these vulnerabilities by severity level, apply evidence-based findings, and suggest specific fixes that integrate with your CI/CD workflow.

How do I automate and structure the code review workflow?

A structured review workflow progresses from automated checks through code, test, and documentation review. This systematic approach reduces friction, ensures consistent quality checks, and can be orchestrated with CI/CD tooling and existing review templates.

What are code smells and how do I identify them in reviews?

Code smells are patterns indicating deeper quality or performance issues. Review patterns help you recognize these anti-patterns, assign appropriate severity levels, and provide constructive feedback that improves both functionality and maintainability.

Can I use code review best practices to train reviewers?

Yes. Structured code-review patterns including feedback templates, severity guidelines, and systematic workflows provide a repeatable framework for reviewer training—ensuring consistent quality standards and collaborative review practices across teams.