autoreview

Runs structured multi-engine code reviews on local, branch, or commit diffs as a closeout check.

1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/JEROME-PRAKASH-L/openclaw --skill autoreview-jerome-prakash-l
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autoreview
Source: https://github.com/JEROME-PRAKASH-L/openclaw/tree/main/.agents/skills/autoreview
Command: npx skills add https://github.com/JEROME-PRAKASH-L/openclaw --skill autoreview-jerome-prakash-l

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? After non-trivial code edits, developers need a reliable second-model review before committing or shipping, but manually bundling diffs, invoking reviewer CLIs, and validating their output is repetitive and error-prone. ## Core Features & Use Cases - Structured Review Helper: Bundles local, branch, or commit diffs and invokes a selected review engine (Codex, Claude, Droid, or Copilot) with validated structured output and clear exit codes. - Review Panels: Runs multiple reviewers against one frozen bundle with per-engine model and thinking/effort settings for higher-risk changes. - Parallel Closeout: Runs focused tests in parallel with the review, with guidance to rerun both until no accepted or actionable findings remain. - Use Case: After fixing a PR branch, run the helper with --mode branch --base origin/main to get a Codex review, verify each finding against the real code, fix accepted issues, and rerun until the helper reports a clean result. ## Quick Start Ask the assistant to run an autoreview on the current branch against origin/main using the default Codex engine and report any accepted findings.

Frequently Asked Questions about autoreview

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

FAQPage Schema
How do I run an automated code review on a PR branch before merging?

Run the autoreview helper with --mode branch --base origin/main, or use the PR's actual base from gh pr view. The helper bundles the diff, calls the selected review engine, and exits nonzero if accepted actionable findings remain.

Which review engine should I use for AI code review?

Codex is the default and recommended engine when nothing is configured, typically giving the best review results. Claude, Droid, and Copilot are also supported via --engine, and multi-reviewer panels are available with --panel or --reviewers.

Can I run tests and code review in parallel?

Yes, pass --parallel-tests with a focused test command to run tests alongside the review. If either leads to code changes, rerun the affected tests and the review until no accepted findings remain.

Why does the review seem stuck for several minutes?

Structured reviews can take up to 30 minutes on large bundles. Heartbeat lines like 'review still running' indicate healthy progress; only investigate after missed heartbeats, the 30-minute window, or an obviously failed subprocess.

How do I review already-committed or pushed changes on main?

Use --mode commit --commit HEAD to review a specific landed commit. Reviewing clean main against origin/main after a push usually produces an empty diff, so target the commit or review the branch before merging.