Code Review

Automate targeted code review of GitHub pull requests for defects and quality issues.

4|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/OpenLabor/openlabor --skill code-review-openlabor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Code Review
Source: https://github.com/OpenLabor/openlabor/tree/main/skills_archive/code-review
Command: npx skills add https://github.com/OpenLabor/openlabor --skill code-review-openlabor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review PRs for quality and bugs, helping teams catch defects, ensure security, and maintain coding standards without manual overhead.

Core Features & Use Cases

  • Automated PR analysis: scans diffs for logical errors, edge cases, and potential regressions.
  • Security & quality checks: highlights vulnerabilities, anti-patterns, and missing tests.
  • Actionable feedback: suggests concrete code changes and rationale to speed up reviews.

Quick Start

Review the latest pull request for quality and bugs.

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 GitHub pull requests to catch bugs and security issues?

Automated code review scans pull request diffs across GitHub repositories to identify logical errors, edge cases, and security vulnerabilities. It applies static analysis checks and style guidelines to provide actionable feedback on code quality.

What is automated PR analysis and how does it handle code quality and security?

Automated PR analysis reviews code changes to highlight vulnerabilities, anti-patterns, and missing tests. It evaluates correctness, edge cases, security, and style by enforcing review criteria against available static analysis checks and test results.

How do I check a pull request for edge cases and style guide violations before merging?

To check a pull request for edge cases and style guide violations, the review process requires static analysis checks, test results, and style guidelines to be available in the PR context. It then scans diffs to enforce these criteria with actionable feedback.

Can I use automated code review across different programming languages in GitHub?

Yes, automated code review applies to pull requests across GitHub repositories and handles multiple programming languages. It targets common review tasks such as correctness, security, and style without manual overhead.

Do I need static analysis tools and test results available to get actionable code review feedback?

Yes, static analysis checks, test results, and style guidelines must be available in the PR context to perform targeted code review. The process uses these inputs to identify defects and suggest concrete code changes with rationale.

Why does automated code review focus on regressions and anti-patterns in pull requests?

Automated code review focuses on regressions and anti-patterns to help teams catch defects and ensure security without manual overhead. It scans diffs to maintain coding standards and suggests concrete code changes to speed up reviews.