claude-code-review

Review pull requests for bugs, security, performance, and test gaps.

108|27|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/diegosouzapw/omni-skills --skill claude-code-review-diegosouzapw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-code-review
Source: https://github.com/diegosouzapw/omni-skills/tree/main/skills/claude-code-review
Command: npx skills add https://github.com/diegosouzapw/omni-skills --skill claude-code-review-diegosouzapw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Automates and standardizes code-review workflows for pull requests by focusing on bugs, security issues, performance concerns, and test gaps, and by posting findings as a PR comment and a formal GitHub review while preserving upstream provenance.

Core Features & Use Cases

  • Focused PR reviews that surface critical issues across bugs, security, performance, and tests.
  • Posts findings to PR as a comment and as a formal GitHub review, maintaining provenance and alignment with upstream workflows.
  • Loads the packaged workflow, support pack, troubleshooting notes, and provenance links to guide handoffs and audits.

Quick Start

Activate the claude-code-review on a PR by providing the PR number or URL and load only the upstream files that matter for the review.

Frequently Asked Questions about claude-code-review

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

FAQPage Schema
How do I automate GitHub pull request reviews for bugs and security issues?

Automated PR reviews focus on bugs, security, performance, and test gaps by evaluating the pull request and posting findings as a PR comment and formal GitHub review.

How does provenance work in automated code review workflows?

Provenance is preserved by operating as an intake wrapper around upstream workflows, loading the packaged support pack, rubric, and router guidance before any review action.

Do I need local tooling to orchestrate pull request reviews?

Yes, orchestrating PR reviews relies on local tooling such as codex-cli, claude-code, cursor, gemini-cli, and opencode to execute the review process.

What is the best way to surface test gaps in GitHub pull requests?

The best way to surface test gaps is using an automated review workflow that loads a specific rubric to identify missing tests and post formal GitHub review comments.

Can I trigger code reviews by providing a pull request URL?

Yes, you can activate the review by providing the PR number or URL, which loads only the upstream files that matter for the review.