Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
bjornmelin avatar

Autoreview

  • 5 installs
  • 5 repo stars
  • Updated August 5, 2026
  • bjornmelin/dev-skills

Autoreview is a Claude Code skill that runs a Codex-only structured code-review closeout over local, branch, or commit diffs with deterministic pass/fail output.

About

Autoreview is a Claude Code skill that runs a Codex-only structured code-review closeout over local, branch, or committed diffs via a bundled helper. It uses codex exec for deterministic pass/fail JSON output and treats findings as advisory, requiring each to be verified against real code before changes. It supports target modes and flags for model, reasoning effort, web search, parallel tests, and output files. Developers use it as a final review gate before committing or shipping.

  • Runs a Codex-only structured code-review closeout for local, branch, or commit diffs
  • Uses codex exec for deterministic pass/fail JSON output, advisory findings
  • Flags: mode, model, reasoning-effort, web-search, parallel-tests, dry-run

Autoreview by the numbers

  • 5 all-time installs (skills.sh)
  • Ranked #881 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

autoreview capabilities & compatibility

Capabilities
code review · security audit · testing
Use cases
code review · testing
From the docs

What autoreview says it does

Run the bundled Codex structured review helper as a closeout check.
SKILL.md
Do not push just to review. Push only when the user requested push, ship, or PR update.
SKILL.md
npx skills add https://github.com/bjornmelin/dev-skills --skill autoreview

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs5
repo stars5
Last updatedAugust 5, 2026
Repositorybjornmelin/dev-skills

What it does

Run a Codex-based structured code-review closeout over a local, branch, or commit diff before committing or shipping.

Who is it for?

Running a final structured Codex review over a diff before commit or ship

Skip if: Pushing code just to trigger review, which the skill explicitly forbids

When should I use this skill?

The user asks for autoreview, a Codex review, or a final structured review before commit or ship

What you get

A structured pass/fail review with verified, actionable findings resolved before shipping.

  • a structured pass/fail review report with accepted findings

By the numbers

  • 3 target modes (local/branch/commit)
  • 4 reasoning-effort levels (low/medium/high/xhigh)

Files

SKILL.mdMarkdownGitHub ↗

Auto Review

Run the bundled Codex structured review helper as a closeout check. Treat the result as advisory: verify every finding against the real code before changing files, and reject speculative or over-broad findings.

Contract

  • Use only the bundled helper; do not run nested review commands.
  • The helper uses codex exec instead of codex review so it can enforce structured JSON output and deterministic pass/fail behavior.
  • Review the intended diff target, not a clean checkout by accident.
  • Keep going until the final helper run reports no accepted/actionable findings.
  • If a review-triggered fix changes code, rerun focused tests and rerun the helper.
  • Report security findings only for concrete, actionable risks introduced or exposed by the change.
  • Do not push just to review. Push only when the user requested push, ship, or PR update.

Pick Target

Dirty local work:

skills/autoreview/scripts/autoreview --mode local

Branch work:

skills/autoreview/scripts/autoreview --mode branch --base origin/main

Committed single change:

skills/autoreview/scripts/autoreview --mode commit --commit HEAD

Use --mode local only when the patch is actually unstaged, staged, or untracked in the current checkout. For committed, pushed, or PR work, review the commit or branch diff instead.

Options

  • --model <model>: pass a Codex model override; omit it to inherit the configured Codex model.
  • --reasoning-effort low|medium|high|xhigh: pass Codex model reasoning effort; omit it to inherit the configured/model default.
  • --web-search: opt into Codex web search for dependency/API/security research; default is off to match Codex review behavior.
  • --prompt / --prompt-file: add task-specific review instructions.
  • --dataset <file>: include extra evidence in the review bundle.
  • --parallel-tests "<command>": run focused tests while Codex reviews the frozen bundle.
  • --output <file> / --json-output <file>: persist human or structured output.
  • --dry-run: print target selection without invoking Codex.

Format first if formatting can change line locations. If tests or review cause edits, rerun the affected tests and rerun autoreview until the helper exits cleanly.

Helper Behavior

The helper:

  • chooses dirty local changes first in --mode auto
  • otherwise uses origin/main for non-main branch review
  • uses codex exec with read-only sandboxing and structured JSON output
  • inherits current Codex model selection by default; keep Codex config on the latest best-fit review model and use --model only for deliberate overrides
  • writes only to stdout unless --output or --json-output is set
  • prints review still running: codex elapsed=<seconds>s pid=<pid> while waiting
  • prints autoreview clean: no accepted/actionable findings reported on a clean result
  • exits nonzero when accepted/actionable findings are present

Final Report

Include:

  • review command used
  • tests/proof run
  • findings accepted/rejected, briefly why
  • the clean result from the final helper run, or why a remaining finding was consciously rejected

Related skills

FAQ

How should autoreview findings be treated?

Treat the result as advisory: verify every finding against the real code before changing files, and reject speculative or over-broad findings.

Which diff target does it review?

It reviews the intended diff target using modes local (unstaged/staged/untracked), branch (against origin/main), or commit (a single committed change like HEAD).

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.