skills.rest
jlaws
jlawsCOMMUNITY
Explore all skills by this author →
GitHub

code-review-patterns

Automate structured PR feedback with phased review and severity labeling.

2|Updated Jan 3, 2026
Search Tags:#feedback#patterns#quality#review#code-review#pull-request
One-click install
npx skills add https://github.com/jlaws/dotfiles --skill code-review-patterns-jlaws
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-patterns
Source: https://github.com/jlaws/dotfiles/tree/main/.agents/skills/workflow/code-review-patterns
Command: npx skills add https://github.com/jlaws/dotfiles --skill code-review-patterns-jlaws

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewing PRs, responding to feedback, and performing self-reviews can be inconsistent and time-consuming; this Skill provides a disciplined, repeatable workflow to improve review quality and consistency.

Core Features & Use Cases

  • Review Mindset and a phased process to guide reviewers through Context, High-Level, and Line-by-Line checks.
  • Severity labeling and structured feedback patterns to improve clarity and reduce back-and-forth.
  • Pre-Submission Diff Review workflow to analyze changes, catch cross-cutting issues, and ensure alignment with project goals.
  • Handling disagreements with constructive strategies and evidence-based justification.

Quick Start

Review a pending PR by following the phased workflow: read the description, assess the scope, evaluate the changes, and finalize feedback.

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 pull request feedback to improve code review quality?▼

You can structure pull request feedback by applying a phased review workflow that covers context, high-level, and line-by-line checks. This approach uses severity labeling and standardized diff analysis to improve code review quality and consistency.

What is the best way to perform a self-review before submitting a PR?▼

The best way to perform a PR self-review is using a pre-submission diff review workflow. This method analyzes your changes, catches cross-cutting issues, and ensures alignment with project goals before requesting feedback from teammates.

How do I handle disagreements during code reviews constructively?▼

Handle code review disagreements constructively by using structured feedback patterns with evidence-based justification. This approach enforces a review mindset that standardizes responses to review comments and reduces inconsistent or time-consuming debates.

Can I apply a standardized diff-analysis framework to any pull request?▼

Yes, you can apply a standardized diff-analysis framework to any pull request. The framework guides reviewers through reading descriptions, assessing scope, and evaluating changes to deliver consistent, structured feedback across varied development workflows.

Why does my code review process lack consistency across different PRs?▼

Your code review process lacks consistency because it does not use a disciplined, repeatable workflow. Implementing a phased review process with severity labeling and structured feedback patterns ensures consistent quality across different pull requests.

Related Skills

Explore More Software Engineering Skills→
williabywilliaby
2

pr-prepare

Generate Markdown pull request descriptions from git status, log, and diffs.

Community
Basic
spencerpaulyspencerpauly
672

babysitting-pr

Monitor open pull requests and resolve CI failures, review comments, and merge conflicts.

Community
Advanced
baphledbaphled
1

static-analysis

Guide static code analysis tools to detect bugs, vulnerabilities, and style violations.

Community
Intermediate
ExpeditoJExpeditoJ

aiox-qa

Automate code review, quality gating, and security analysis for software projects.

Community
Intermediate