code-review

Review code changes for correctness, readability, architecture, security, and performance.

4|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/rbaumier/skills --skill code-review-rbaumier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/rbaumier/skills/tree/main/code-review
Command: npx skills add https://github.com/rbaumier/skills --skill code-review-rbaumier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide a consistent, checklist-driven process to request, conduct, and act on code reviews so teams catch design, correctness, security, and performance issues before merge and reduce review friction and rework.

Core Features & Use Cases

  • Pre-review hygiene: enforce CI green, self-check list, and scope/diff-size guidance to avoid noisy reviews.
  • Five-axis evaluation: structured review across correctness, readability, architecture, security, and performance with tests-first emphasis.
  • Clear triage and response: standardized severity labels, verification steps, and a response pattern for receiving and implementing feedback.
  • Use case: submit a PR for a feature change and get an actionable review that highlights blocking bugs, test gaps, security exposures, and suggested refactors with severity tags.

Quick Start

Ask the skill to review a pull request by giving base and head SHAs, a short description of what changed, tests performed, and known risks.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I conduct a structured code review for a pull request?

To conduct a structured code review, provide the base and head SHAs, a description of the changes, tests performed, and known risks. The review evaluates code across correctness, readability, architecture, security, and performance, returning labeled findings with severity and recommended fixes.

What is the best way to check pull request security and performance before merge?

Checking pull request security and performance requires a multi-axis evaluation that identifies vulnerabilities and detects issues like n-plus-one queries. This process provides labeled findings with severity tags, recommended fixes, and verification steps including CI checks to ensure software quality before merge.

Can I use an automated code review process for CI pipelines?

Yes, you can use an automated code review process for CI pipelines. CI review agents can apply this structured evaluation to commit ranges and diffs, checking for test gaps, blocking bugs, and security exposures to enforce software quality before integration.

How do I triage code review findings and prioritize fixes?

To triage code review findings, use standardized severity labels assigned to each issue across five evaluation axes. This triage process highlights blocking bugs and suggests refactors, providing a clear response pattern for implementing feedback and running verification steps.

What should I check before submitting a pull request for review?

Before submitting a pull request for review, ensure pre-review hygiene by verifying CI is green, completing a self-check list, and managing the scope and diff size. This preparation avoids noisy reviews and reduces friction and rework during the architecture and security assessment.