skills.rest
arozumenko
arozumenkoCOMMUNITY
Explore all skills by this author →
GitHub

code-review

Review staged diffs, working-tree changes, and GitHub pull request diffs for correctness, security, performance, and maintainability.

18|9|Updated Apr 8, 2026
Search Tags:#code review#performance#security#maintainability#GitHub PR#correctness
One-click install
npx skills add https://github.com/arozumenko/sdlc-skills --skill code-review-arozumenko
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/arozumenko/sdlc-skills/tree/main/skills/code-review
Command: npx skills add https://github.com/arozumenko/sdlc-skills --skill code-review-arozumenko

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code changes often ship with subtle correctness bugs, security weaknesses, performance regressions, or maintainability problems that are hard to spot during quick reviews.

Core Features & Use Cases

  • Risk-focused checklist: Reviews correctness first, then security, concurrency/state, performance, and maintainability.
  • Flexible review triggers: Supports staged changes, working tree changes, and GitHub PR diffs, including targeted file review.
  • Structured output: Produces a summary, categorized issues with file/line references, and clarification questions.

Quick Start

Ask your AI IDE to review the PR or diff and produce a prioritized list of critical, important, and nit issues with file paths and suggested fixes.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review a GitHub PR diff for correctness and security issues?▼

Reviewing staged or working-tree changes involves inspecting diffs against a prioritized checklist covering correctness, security, concurrency, performance, and maintainability, producing structured issues with file paths and severities.

What is the best way to catch performance regressions and state issues in staged changes?▼

Catching performance regressions and state issues requires applying a risk-focused checklist to staged changes, categorizing identified bottlenecks and concurrency problems by severity with specific file and line references.

Can I review targeted files in a working tree diff instead of the entire codebase?▼

Yes, you can review targeted files within working tree changes. The process supports inspecting specific file paths in diffs to focus scrutiny on correctness, security, and maintainability without reviewing unrelated code.

Does automated code review provide structured output with file and line references?▼

Automated code review provides structured output by generating a summary alongside categorized issues. Each issue includes specific file and line references, severity levels, suggested fixes, and clarification questions.

How do I avoid style-only feedback when reviewing pull requests?▼

To avoid style-only feedback during pull request reviews, apply guardrails that focus strictly on correctness, security, performance, and maintainability, explicitly ignoring unrelated refactor suggestions or purely stylistic preferences.

Related Skills

Explore More Software Engineering Skills→
klaidliadonklaidliadon

codex-review

Review pull requests, files, and local diffs with Codex.

Community
Advanced
peancharoenpeancharoen

speckit.reviewer

Review git diffs and file paths for code issues with severity labels.

Community
Intermediate
uukuguyuukuguy
1

issue-detection

Detect code issues across security, quality, performance, and maintainability dimensions.

Community
Advanced
bradtaylorsfbradtaylorsf
8

pr-review

Analyze pull request code diffs for security, correctness, performance, and maintainability.

Community
Advanced