autoreview

Executes structured code reviews across local, branch/PR, and committed Git workflows.

5|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/p-sree-sai-pavan/P.A.R.K.E.R --skill autoreview-p-sree-sai-pavan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autoreview
Source: https://github.com/p-sree-sai-pavan/P.A.R.K.E.R/tree/main/gateway/.agents/skills/autoreview
Command: npx skills add https://github.com/p-sree-sai-pavan/P.A.R.K.E.R --skill autoreview-p-sree-sai-pavan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Auto Review closeout. Codex review is the default when no engine is set and is the recommended reviewer.

Core Features & Use Cases

  • Structured advisory reviews: run a consistent, rule-based review pass without applying fixes automatically.
  • Workflow flexibility: supports local changes, branch/PR reviews, and committed history across multiple contexts.
  • Configurable engines & reporting: allows selection of review engines, prompts, and outputs a final report when no actionable items remain.

Quick Start

Run autoreview in your project directory to start a local, structured code review against your latest changes.

Frequently Asked Questions about autoreview

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

FAQPage Schema
How do I automate structured code reviews for local changes?

You can automate structured code reviews for local changes by running the autoreview helper in your project directory. It performs a consistent, rule-based review pass against your latest work without applying fixes automatically.

Does this code review automation support branch and PR reviews?

Yes, code review automation supports local changes, branch reviews, and PR reviews. It ensures reviews remain consistent across different workflows and can also evaluate committed history.

How do I configure the review engine for my git workflow?

You can configure the review engine by explicitly setting it in your environment, as safe usage patterns require explicit engines or prompts. Codex review is the default when no engine is set.

What happens when a structured code review finds no actionable issues?

When a structured code review finds no actionable issues, it produces a final clean report. This ensures your code passes the advisory review and is ready for the next workflow stage.

Are there limitations to using automated advisory code reviews?

A limitation of automated advisory code reviews is that they do not apply fixes automatically; they only generate actionable findings. You must explicitly configure an engine or prompt to run the review safely.