code-review

Reviews Git branch diffs for correctness, conventions, and architecture with cited checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you perform reliable code reviews by ensuring the review is grounded in the correct base branch, scoped strictly to the branch diff, and supported by evidence for any affirmative claims.

Core Features & Use Cases

  • Base branch determination: Selects the correct comparison base using PR/MR targets, upstream tracking, or merge-base heuristics, and asks for clarification when uncertain.
  • Strict in-scope diff review: Reviews only commits contained within the branch, using git diff <base>...HEAD to avoid flagging pre-existing issues.
  • Review integrity and auditability: Enforces commit-message coherence, commit-message style audits, and citation of concrete checks before making verified claims.
  • Targeted tone and signal control: Encourages colleague-like phrasing and avoids noise, focusing on important correctness, maintainability, and architectural constraints.
  • Sub-agent safe delegation guidance: Instructs delegating reviewers to use git diff output so they can distinguish branch changes from historical code patterns.
  • Test coverage philosophy: Requests coverage for business logic, integration points, error paths, and custom algorithms while trusting well-maintained external libraries.

Quick Start

Ask the skill to run a review for your branch by providing the branch name or the PR/MR URL so it can determine the correct base and review the in-scope diff.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review only the new changes in a git pull request without flagging pre-existing code?

To review only new changes in a git pull request, derive the correct base branch and scope the review strictly to the branch diff using git diff base...HEAD, ignoring pre-existing issues.

What is the best way to determine the correct base branch for a scoped code review?

Determining the correct base branch for a code review uses PR targets, upstream tracking, or merge-base heuristics, asking for clarification when uncertain to ensure accurate comparison scoping.

How do you audit commit messages for coherence and style during a pull request review?

Auditing commit messages during a pull request review involves checking commit-message coherence and enforcing style audits to ensure the branch history maintains consistent conventions.

Does automated code review check test coverage for custom algorithms and error paths?

Automated code review checks test coverage by requesting coverage for business logic, integration points, error paths, and custom algorithms, while trusting well-maintained external libraries.

Can I use sub-agents to delegate git diff code reviews without losing branch context?

You can delegate git diff code reviews to sub-agents by providing them the git diff output, which allows them to distinguish branch changes from historical code patterns safely.