← Back to Engineering & QA

Review a pull request

Compare review-only, checklist-driven, and feedback-handling workflows for a concrete diff or pull request.

Last meaningful review July 20, 2026

The job

You have a pull request or code diff and need prioritized, evidence-linked feedback on correctness, quality, risk, and maintainability.

Includedlocal diff or pull-request review · correctness and code-quality findings · review feedback handling

Not this pageunscoped repository audit · automatic large refactor · full penetration test

30-second route

01

You have a local diff, branch, or PR branch and want a scope-controlled review/fix loop.

It directly documents local, branch, and commit review modes plus validation and rerun discipline.

Editorial confidence: high
Consider Autoreview
02

You have a GitHub PR number or URL and want PR context plus an explicit approval/request-changes conclusion.

It explicitly targets remote PRs, reads their context, and returns categorized findings with a clear conclusion.

Editorial confidence: high
Consider Code Reviewer
03

You are reviewing the current editor session and want comments anchored to exact changed-code ranges without modifications.

Its declared output is inline, exact-range review comments and it prohibits writes.

Editorial confidence: high
Consider Code Review
04

The request expands into a full penetration test or unscoped repository audit.

Those scopes are excluded from this task.

Editorial confidence: high
Do not use these review skills as a substitute.

Before you install

Install Autoreview; adapt Code Reviewer to the repository's verification command; use VS Code Code Review only where its inline-comment tool is available.

All three have explicit source-backed review workflows, but their setup assumptions differ.

Read the intervention guide →

Source-led comparison

What changes the choice

Facts are extracted from each selected Skill’s declared workflow. Signals describe public adoption; they are not a universal score.

Source notes

Inspect evidence and candidate limits 3 candidates

Why these candidatesEach candidate comes from tracked public sources and has a source-attributed adoption signal. This is a shortlist, not a catalogue or global ranking.

What this cannot establishWe read declared instructions and public signals. We do not run skills, benchmark outputs, audit security, or claim a universal best choice.

01

Autoreview

Source ↗

Use it forA structured closeout review of a local diff, branch, or PR branch, especially when review findings need validation and follow-up handling.

Avoid ifYou need review comments directly in an editor UI or a GitHub-specific submission workflow.

ActionInstall

EditsNone indicated.

SetupSet the documented AUTOREVIEW script path, then choose local, branch, or commit mode.

Inspect workflow and compatibility details

ContextHighest-ranked directly applicable finalist (SkillsMP Popular rank 12). It explicitly supports reviewing local and PR branches, includes correctness/security review, and treats findings as advisory until verified.

OutputValidated structured review findings; a clean result is successful helper exit with no accepted/actionable findings.

ControlScope-governed closeout gate: verify findings against code and dependencies, keep fixes in scope, retest and rerun review after accepted changes.

Invocation"$AUTOREVIEW" --mode branch --base origin/main

Install scopeProject-local, source checkout, or global paths are documented.

Agent fitStrong for agents working from a repository checkout and handling an iterative review/fix cycle.

Watch outThe review is advisory and may take substantial time for large bundles; it is not proof of user-visible behavior.

Source-visible capabilitiesReview targetsReviews dirty local work, branch/PR work, and single committed changes.explicit sourceFinding handlingRequires verification of each finding and focused tests plus another review after a review-triggered code change.explicit source
CompatibilityWindowsdeclarednot runtime-testedUnix-like shellsdeclarednot runtime-tested
Evidence

The skill is a structured code-review closeout check for local or PR branches.SKILL.md:8-19 · inspected 2026-07-20 · high confidence

Findings must be verified, kept in scope, and followed by focused tests and a rerun when accepted changes alter code.SKILL.md:22-30 · inspected 2026-07-20 · high confidence

It documents local, branch/PR, and commit targets.SKILL.md:147-190 · inspected 2026-07-20 · high confidence

Public signal12 /SkillsMP source-specifictop-choicestructured-reviewlocal-and-branch-reviewscope-controlexplicit source
02

Code Reviewer

Source ↗

Use it forA complete local or remote pull-request review that needs PR context, categorized feedback, and an approval/request-changes recommendation.

Avoid ifChecking out a remote PR or running a project preflight would be inappropriate for the review environment.

ActionInstall

EditsNone indicated.

SetupFor a remote PR, use GitHub CLI checkout, run the project's stated preflight, and read the PR description and existing comments.

Inspect workflow and compatibility details

ContextDirectly covers both remote PRs and local changes, with an explicit review checklist across correctness, maintainability, security, edge cases, and tests. Its SkillsMP Popular rank is 146.

OutputSummary, categorized findings (Critical, Improvements, optional Nitpicks), and an Approved or Request Changes conclusion.

ControlProfessional review workflow with explicit target selection, preparation, deep-analysis pillars, and cleanup confirmation for remote PRs.

InvocationReview PR #123

Install scopeNot yet mapped from the source.

Agent fitStrong for an agent that can use GitHub CLI and should give a formal, author-facing review report.

Watch outThe source assumes `npm run preflight` for remote PRs, so projects with different verification commands need adaptation.

Source-visible capabilitiesTarget selectionSupports remote PRs by number or URL and staged or unstaged local changes.explicit sourceReview coverageChecks correctness, maintainability, readability, efficiency, security, error handling, and testability.explicit source
CompatibilityGitHub repositoriesdeclarednot runtime-testedLocal git worktreesdeclarednot runtime-tested
Evidence

It explicitly supports both local changes and remote pull requests.SKILL.md:3-11 · inspected 2026-07-20 · high confidence

The remote-PR workflow checks out the PR, runs preflight, and reads description and existing comments.SKILL.md:21-30 · inspected 2026-07-20 · high confidence

Its analysis pillars and feedback format cover the requested review dimensions and conclusion.SKILL.md:38-65 · inspected 2026-07-20 · high confidence

Public signal146 /SkillsMP source-specificremote-prlocal-changeschecklist-drivenformal-verdictexplicit source
03

Code Review

Source ↗

Use it forA review-only pass over the current session's changed files when inline, exact-range comments are the desired deliverable.

Avoid ifYou need a workflow for fetching a remote PR, executing checks, or implementing fixes after review.

ActionInstall

EditsNone indicated.

SetupRun from a session where changed files and an inline `addComment` capability are available.

Inspect workflow and compatibility details

ContextA directly applicable, constrained review-only substitute with the second-best public-recognition signal among the selected options (SkillsMP Popular rank 47). It is narrower than the other two because it targets the current session's changes.

OutputOnly inline comments attached to exact file URIs and line ranges.

ControlHigh-signal, non-mutating review: inspect changed files in repository context, comment only on concrete issues, then stop.

InvocationUse via the Changes toolbar's Run Code Review action.

Install scopeNot yet mapped from the source.

Agent fitBest for VS Code-style review sessions with an inline-comment tool.

Watch outIt is explicitly tied to current-session changes and requires the `addComment` tool; the source does not describe remote PR retrieval.

Source-visible capabilitiesReview checksReviews correctness, edge cases, regressions, security, clarity, consistency, and test/documentation gaps.explicit sourceInline feedbackAttaches each issue to an exact file URI and line range, favoring fewer high-signal comments.explicit source
CompatibilityVS Code current-session reviewdeclarednot runtime-testedOther environmentslimitednot runtime-tested
Public signal47 /SkillsMP source-specificreview-onlyinline-commentscurrent-sessionnon-mutatingexplicit source

Still comparing?

Tell us the job, not just the skill names.

Request a task guide
Did this decision map help?