code-review

Evaluate code changes and generate prioritized actionable feedback.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewing code changes can be error-prone and inconsistent. This Skill provides a structured process and guidelines to help engineers perform thorough, repeatable code reviews, improving quality, security, and maintainability.

Core Features & Use Cases

  • Change Discipline: enforces minimal, focused edits to prevent scope creep.
  • Investigation & Feedback Flow: step-by-step approach to identify issues, gather evidence, and report actionable feedback.
  • Review Workflow Guidance: clear steps from context gathering to delivering feedback, ensuring consistency across reviews.
  • Use Case: when reviewing a pull request, run the skill to generate a prioritized list of issues (critical, important, suggestions) with recommended fixes.

Quick Start

Use the code-review skill to review a PR by providing the PR URL or git diff, for example: Review PR https://github.com/your/repo/pull/123 or describe the changes with git diff.

Frequently Asked Questions about code-review

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

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

Automating code review for a pull request involves providing the PR URL or git diff to generate a prioritized list of actionable feedback. The process evaluates security, performance, testing, and design to ensure consistent quality checks.

What is the best way to structure pull request feedback?

Structuring pull request feedback requires a prioritized format separating issues into critical, important, and suggestions. This enforces a repeatable review process by guiding reviewers through a defined checklist of engineering best practices and design considerations.

Can I review a git diff for security and performance issues?

Reviewing a git diff for security and performance issues is achieved by applying a structured evaluation checklist to the provided patch set. This identifies vulnerabilities and bottlenecks while enforcing minimal, focused edits to prevent scope creep.

How do I prevent scope creep when reviewing code changes?

Preventing scope creep when reviewing code changes is handled by enforcing a change discipline that demands minimal, focused edits. The review workflow guides evaluators from context gathering to delivering actionable feedback, ensuring changes remain targeted.

Does automated code review work without connecting a repository?

Automated code review works without directly connecting a repository by accepting pasted git diffs or patch sets as input. You can describe the changes directly to evaluate testing coverage and design considerations without needing live repository access.

What are the limitations of using a checklist for code reviews?

Limitations of using a checklist for code reviews include its basic implementation depth, which provides structured guidance but relies on the reviewer to supply accurate diffs. It does not automatically fetch changes or execute automated tests.