Skills Guide

Code Review and PR Review

VerifiedSafe

Skill for code review and PR review, focusing on substantive issues while skipping style nitpicks.

Download and use
Sby Skills Guide Bot
DevelopmentIntermediate
8/6/2026
Claude CodeCursorCodex
#code-review#pull-request#github#code-quality#review-methodology

Recommended for

Backend developerClaude CodeCode reviewFrontend developerCursorFullstack developer

Automated summary

Provides a structured methodology for reviewing a GitHub pull request, prioritising substantive issues and reporting findings with explicit severity levels.

Strengths

  • Clear priority order (correctness, security, reliability, performance, breaking changes, test coverage) that keeps the review focused
  • Enforced output format with blocking/non-blocking severity, file:line location and a concrete suggested fix
  • Explicitly instructs reading surrounding code first, reducing false positives caused by established conventions
  • Deliberately skips style and formatting so attention stays on consequential problems

Limitations

  • Relies on the `gh` CLI and assumes an accessible GitHub remote with sufficient permissions
  • Describes no test execution or automated checks; the analysis stays static
  • The blocking versus non-blocking judgement is left to the model's discretion, with no numeric rubric
When to use it

Reach for it when a pull request needs a merge-readiness assessment and you want a prioritised verdict rather than a stream of stylistic remarks.

When not to use it

Skip it for reviewing local code that is not hosted on GitHub, or for pure reformatting requests, which the skill intentionally ignores.

Security analysis

Safe
Quality score88/100

The skill instructs running GitHub CLI commands (gh pr view, gh pr diff) to fetch pull request data and diffs for review purposes. This is a legitimate use of network access and does not involve destructive actions, exfiltration, obfuscation, or disabling safety. No sensitive data is transmitted outside the normal GitHub context.

No concerns found

How this analysis is made

Examples

Pre-merge PR review
Review PR #482 in acme/api before I merge it. Flag anything blocking and give me a suggested fix for each issue.
Security-focused review
Do a code review of the open pull request that touches the payment retry logic — I care most about correctness and security.
Triage a large diff
Use gh to pull the diff for PR #91 and tell me whether it's ready to merge, separating blocking issues from optional suggestions.

name: code-review description: Use this skill for code review and PR review tasks. Covers review methodology, what to flag, what to skip, and output structure.

Code Review

Review a GitHub pull request for substantive issues. Focus on what matters, skip what doesn't.

Steps

  1. Run gh pr view {pr_number} --json title,body,files to understand the PR's purpose and scope.
  2. Run gh pr diff {pr_number} to read the full diff.
  3. Before commenting, read surrounding code to understand full context — a pattern that looks wrong in isolation may be an established convention.

Focus Areas (priority order)

  1. Correctness — Logic bugs, edge cases, error handling
  2. Security — Input validation, injection risks, secrets exposure
  3. Reliability — Race conditions, failure modes, resource leaks
  4. Performance — Inefficient algorithms, N+1 queries, unnecessary work
  5. Breaking changes — API/behavior changes affecting callers
  6. Test coverage — Are new code paths tested?

Skip style/formatting unless it materially impacts readability. Do not nitpick naming, style preferences, or issues linters catch.

Severity Levels

  • Blocking: Must fix before merge (bugs, security, significant reliability/performance issues, breaking changes)
  • Non-blocking: Suggestions for improvement (optional)

Output Format

Findings

For each issue found:

[Issue Title]

  • Severity: blocking | non-blocking
  • Location: file_path:line_number
  • Description: What the issue is and why it matters
  • Suggested Fix: Concrete code change or approach

If no issues found, state that the changes look correct and explain why.

Summary

Overall assessment: is the PR ready to merge, or does it need changes? List the most important issues if any.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/code-review-and-pr-review-msh3uscu/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/code-review-and-pr-review-msh3uscu' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/code-review-and-pr-review-msh3uscu/download' --output '.skill-downloads/code-review-and-pr-review-msh3uscu/SKILL.md.part' && mv '.skill-downloads/code-review-and-pr-review-msh3uscu/SKILL.md.part' '.skill-downloads/code-review-and-pr-review-msh3uscu/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/code-review-and-pr-review-msh3uscu/SKILL.md' && test -s '.skill-downloads/code-review-and-pr-review-msh3uscu/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/code-review' && cp -R '.skill-downloads/code-review-and-pr-review-msh3uscu' '.claude/skills/code-review'

Cursor
test -f '.skill-downloads/code-review-and-pr-review-msh3uscu/SKILL.md' && test -s '.skill-downloads/code-review-and-pr-review-msh3uscu/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/code-review' && cp -R '.skill-downloads/code-review-and-pr-review-msh3uscu' '.cursor/skills/code-review'

Codex
test -f '.skill-downloads/code-review-and-pr-review-msh3uscu/SKILL.md' && test -s '.skill-downloads/code-review-and-pr-review-msh3uscu/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/code-review' && cp -R '.skill-downloads/code-review-and-pr-review-msh3uscu' '.agents/skills/code-review'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/code-review-and-pr-review-msh3uscu'

openskills read 'code-review-and-pr-review-msh3uscu'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/code-review-and-pr-review-msh3uscu/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

Emotion to Mantine Migration

Development

Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

Scope Creep Detector

Development

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot