claude-code-review

Review GitHub pull requests and post comments with test and linter evidence.

470|26|Updated Oct 6, 2023
One-click install
npx skills add https://github.com/DataRecce/recce --skill claude-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-code-review
Source: https://github.com/DataRecce/recce/tree/main/.claude/skills/claude-code-review
Command: npx skills add https://github.com/DataRecce/recce --skill claude-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many code reviews are time-consuming and inconsistent; this Skill provides a focused, automated review that surfaces critical bugs, security issues, performance regressions, and test gaps so maintainers can quickly act with confidence.

Core Features & Use Cases

  • Automated PR parsing and analysis: Extracts PR number or URL, fetches PR metadata and diffs, and reads changed files in full context.
  • Evidence-backed verification: Runs relevant tests, linters, and type checks for concrete failure evidence to include in findings.
  • GitHub integration: Posts or updates a hidden-marked review comment and submits a formal GitHub review approving or requesting changes.
  • Use Case: Use when a repository maintainer or reviewer needs a fast, consistent assessment of critical issues on a pull request before merging.

Quick Start

Invoke the claude-code-review skill with a pull request number or URL like /claude-code-review 123 to run an automated review and post results to GitHub.

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 pull request reviews on GitHub to detect bugs and security vulnerabilities?

Automated pull request reviews parse PR diffs and metadata to detect bugs, security vulnerabilities, and performance regressions. By running tests and linters for evidence, the review process surfaces critical issues and test gaps directly on GitHub.

What is the best way to run tests and linters automatically when a new pull request is opened?

Automated PR analysis fetches the changed files in full context, runs relevant tests and linters to gather concrete failure evidence, and posts actionable review comments. This ensures maintainers receive evidence-backed verification directly on the pull request.

Can I use automated code review to check for missing tests and performance regressions before merging?

Yes, automated code review detects missing tests and performance regressions during PR evaluation. It checks out PR branches, runs relevant tests and linters, and submits a formal GitHub review approving or requesting changes based on the findings.

How do I post actionable GitHub review comments automatically from a PR analysis tool?

PR analysis tools post actionable GitHub review comments by fetching the PR diff, running verification checks, and creating or updating hidden-marked review comments. They submit a formal GitHub review to approve or request changes based on the automated findings.

Does automated code review require access to checkout PR branches and fetch metadata?

Yes, automated code review requires access to PR metadata and diffs, the ability to fetch and checkout PR branches, and permissions to create or update GitHub comments. This access allows the tool to read changed files in full context and run relevant tests.

How does an automated PR reviewer handle existing bot comments on a pull request?

An automated PR reviewer detects prior bot comments on a pull request and updates the existing hidden-marked review comment rather than creating duplicates. This ensures the GitHub review history remains clean and reflects the latest automated analysis.