skills.rest
sjoerdbeentjes
sjoerdbeentjesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

code-review

Identify issues in code changes and return structured feedback.

Updated Apr 14, 2026
Search Tags:#git#feedback#diff#quality-assurance#code-review#pull-request#coding-quality
One-click install
npx skills add https://github.com/sjoerdbeentjes/open-agents --skill code-review-sjoerdbeentjes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/sjoerdbeentjes/open-agents/tree/main/.agents/skills/code-review
Command: npx skills add https://github.com/sjoerdbeentjes/open-agents --skill code-review-sjoerdbeentjes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews code changes and provides actionable feedback to accelerate quality and reduce review cycles.

Core Features & Use Cases

  • Determine review scope based on diff, commit, branch, or PR.
  • Provide structured feedback focusing on bugs, logic, tests, style, and security.
  • Guide how to inspect changed files in full context and avoid false positives.

Quick Start

Review the latest changes in the current branch or PR and return actionable feedback.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I get actionable feedback on a git pull request?▼

Code review identifies issues in code changes to provide actionable feedback, evaluating logic, edge cases, readability, tests, and security to ensure quality across diffs, commits, branches, and pull requests.

What is the best way to review a diff for bugs and security issues?▼

Reviewing a diff for bugs and security involves inspecting changed files in full context to avoid false positives, evaluating logic, edge cases, readability, tests, and conformance to project conventions.

Can I use automated code review across different programming languages?▼

Yes, code review is applicable across languages, files, and repositories, evaluating logic, edge cases, readability, tests, security considerations, and project conventions to return structured feedback.

How do I determine the scope of a code review for a specific branch?▼

You can determine code review scope based on a diff, commit, branch, or pull request, ensuring feedback focuses on relevant logic, tests, style, and security changes within that boundary.

How do I avoid false positives when reviewing code changes?▼

To avoid false positives when reviewing code changes, inspect the changed files in their full context, ensuring accurate evaluation of logic, edge cases, readability, and project convention adherence.

Related Skills

Explore More Software Engineering Skills→
SpillwaveSolutionsSpillwaveSolutions
46

pr-reviewer

Collect GitHub PR data and generate structured review files with two-stage approval.

Official
Advanced
jaisonerickjaisonerick

fix-bugs

Reproduce QA-reported failures with failing tests and apply minimal code fixes.

Community
Advanced
eliottbusinesseliottbusiness

requesting-code-review

Automate pre-commit code review with static analysis and security scanning.

Community
Advanced
SantiagoisperSantiagoisper

lfg

Automate the full engineering pipeline from planning to CI loop.

Community
Advanced