code-review

Analyze code changes and provide actionable feedback on defects, style, and design.

5.8k|755|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/vercel-labs/open-agents --skill code-review-vercel-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/vercel-labs/open-agents/tree/main/.agents/skills/code-review
Command: npx skills add https://github.com/vercel-labs/open-agents --skill code-review-vercel-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly assess code changes and provide actionable feedback to improve quality before merging.

Core Features & Use Cases

  • Review diffs and full files to spot bugs, style issues, and edge cases.
  • Provide prioritized feedback with concrete suggestions for fixes.
  • Support for PRs, commits, and branch comparisons across repositories to accelerate review cycles.

Quick Start

Submit the diff or PR URL to receive a structured, actionable code review.

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 code review feedback on a pull request?

To review a pull request for bugs and design flaws, submit the PR URL or diff for static analysis. The review prioritizes correctness, maintainability, and security, providing structured feedback and suggested fixes for code changes.

What is the best way to review code changes for security and maintainability before merging?

The best way to review code changes for security and maintainability is applying static analysis patterns to branch comparisons. This assesses correctness and design across repositories, accelerating review cycles with prioritized, actionable feedback before merging.

Can I use static analysis to check code quality across different repository branch comparisons?

Yes, static analysis can check code quality across different repository branch comparisons. It analyzes full files and diffs to spot edge cases and style issues, structuring feedback to improve overall code quality and maintainability.

Does code review work with diffs from commits or only full pull requests?

Code review works with both individual commit diffs and full pull requests. It analyzes the provided code changes to identify defects and design issues, applying static analysis patterns to deliver prioritized, actionable suggestions for fixes.

What limitations should I expect when using automated static analysis for pull request reviews?

Automated static analysis for pull request reviews focuses on defects, style, and design within diffs, but may miss complex runtime context. It provides structured feedback and suggested fixes, yet requires human validation for broader architectural edge cases.