skills.rest
xinbenlv
xinbenlvCOMMUNITY
Explore all skills by this author →
Website𝕏@ZainanZhouGitHub

general-codereview

Guide pull request reviews through a five-step Google-inspired workflow.

8|Updated Jan 14, 2026
Search Tags:#code review#maintainability#quality#diff#PR review#Google
One-click install
npx skills add https://github.com/xinbenlv/codereview-skills --skill general-codereview
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: general-codereview
Source: https://github.com/xinbenlv/codereview-skills/tree/main/skills/general-codereview
Command: npx skills add https://github.com/xinbenlv/codereview-skills --skill general-codereview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides reviewers through a standardized, Google-inspired code review workflow for evaluating pull requests and diffs.

Core Features & Use Cases

  • Pre-screen a code change to assess size and relevance.
  • Understand the change from the author's perspective, clarifying purpose and context.
  • Verify that the implementation matches the description and tests.
  • Optimize for readability, maintainability, and performance.
  • Check style and conformance to project guidelines across languages and repos.

Quick Start

Review a PR or change list using the general-codereview skill to guide your evaluation of the diff.

Frequently Asked Questions about general-codereview

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

FAQPage Schema
How do I perform a Google-style code review on a pull request?▼

A standardized code review workflow improves maintainability by guiding you through Pre-screen, Understand, Verify, Optimize, and Check steps to evaluate pull requests systematically, ensuring changes are assessed for readability and project conformance.

What is the best way to structure PR review for maintainability across different languages?▼

The best way to structure PR review across languages is using a standardized workflow that pre-screens change size, verifies implementation matches tests, and checks style conformance to project guidelines for optimal readability.

How do I verify that a code change matches its description and tests during a diff review?▼

To verify a code change during a diff review, this skill applies an evaluation step to ensure the implementation matches the author's description and associated tests before optimizing for performance and readability.

Can I use a standardized code review workflow for any repository or programming language?▼

Yes, you can use this standardized code review workflow across any repository or programming language because it applies a language-agnostic process to check style, conformance, and maintainability for every pull request.

What steps should I follow to evaluate a pull request diff for correctness and quality?▼

You should follow five steps to evaluate a pull request diff: Pre-screen the change size, Understand the author's context, Verify the implementation, Optimize for readability, and Check style conformance to ensure overall code quality.

Related Skills

Explore More Software Engineering Skills→
edobryedobry
6

review-pr

Analyze pull requests and post structured GitHub PR reviews.

Community
Advanced
sun2443sun2443

code-review

Review code changes for security, performance, and correctness issues.

Community
Intermediate
jtucker9jtucker9

verify

Verify completed work with automated build, test, and lint checks before committing.

Community
Advanced
lxh755818-botlxh755818-bot

requesting-code-review

Automate pre-commit code review with security scans, linting, and testing.

Community
Advanced