review

Review code changes for correctness, consistency, and safe integration.

1|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/BenchAGI/bench-cowork --skill review-benchagi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/BenchAGI/bench-cowork/tree/main/skills/review
Command: npx skills add https://github.com/BenchAGI/bench-cowork --skill review-benchagi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews pull requests and changes to ensure correctness, patterns, naming, tests, and blast radius align with Bench monorepo conventions and CLAUDE.md guidelines.

Core Features & Use Cases

  • Evaluate correctness and conformance to repo conventions (CLAUDE.md)
  • Assess patterns, naming, tests, and blast radius to prevent regressions
  • Use during code review or before merging non-trivial changes to the monorepo

Quick Start

Review the latest diff for adherence to repository conventions and the CLAUDE.md standards.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a pull request for correctness and blast radius before merging?

Reviewing a pull request involves evaluating code changes for correctness, patterns, naming, tests, and blast radius to ensure safe integration and prevent regressions in non-trivial changes.

What does a code diff review cover for safe integration?

A code diff review covers correctness, consistency, naming conventions, test coverage, blast radius, and conformance to repository standards like CLAUDE.md to ensure safe integration.

Can I use this to check local diffs against Bench monorepo conventions?

Yes, you can apply this review to local diffs and pull requests in the Bench monorepo to verify adherence to CLAUDE.md guidelines and repository conventions for safe integration.

When do I need an automated code review for non-trivial changes?

You need an automated code review when merging non-trivial changes to the monorepo, ensuring correctness, pattern adherence, and blast radius assessment to prevent regressions.

What's the best way to ensure code changes conform to CLAUDE.md standards?

The best way to ensure conformance is to review the latest diff against CLAUDE.md standards, checking correctness, patterns, naming, tests, and blast radius for safe integration into the monorepo.