skills.rest
swyxio
swyxioCOMMUNITY
Explore all skills by this author →
Website𝕏@swyxGitHub

autoreview

Run structured closeout code reviews on branches, PRs, and commits.

154|9|Updated Mar 27, 2026
Search Tags:#code review#software quality#review automation#pre-merge check#codex review#PR validation#closeout review
One-click install
npx skills add https://github.com/swyxio/skills --skill autoreview-swyxio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: autoreview
Source: https://github.com/swyxio/skills/tree/main/autoreview
Command: npx skills add https://github.com/swyxio/skills --skill autoreview-swyxio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of inconsistent, incomplete code reviews before merging, shipping, or releasing code by providing a standardized, structured closeout workflow for non-trivial edits, branch work, and commits.

Core Features & Use Cases

  • Structured Closeout Review: Runs a validated, helper-driven code review after non-trivial code changes, PR work, or commits, with support for multiple review engines including Codex and Claude.
  • Flexible Review Modes: Supports local dirty change reviews, branch/PR diff reviews, and single commit reviews, with optional multi-reviewer panels for high-risk changes.
  • Use Case: Before merging a feature branch with multiple non-trivial changes, use this Skill to run a final review, verify all accepted findings, rerun focused tests if fixes are made, and confirm no actionable issues remain before shipping.

Quick Start

Use the autoreview skill to run a structured final code review on your current branch before merging to confirm no actionable issues remain.

Frequently Asked Questions about autoreview

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

FAQPage Schema
How do I run a structured code review before merging a feature branch?▼

Run a structured closeout code review on your feature branch to validate post-edit changes, verify accepted findings, and rerun focused tests after review-triggered fixes. This confirms no actionable issues remain before merging or shipping code.

What is a closeout code review and when do I need one?▼

A closeout code review is a final validation pass for non-trivial code edits and branch work. You need it before committing, merging, shipping, or releasing code to eliminate inconsistent pre-ship validation and confirm no actionable issues remain.

Can I use multiple review engines for pre-merge PR validation?▼

Yes, pre-merge PR validation supports multiple review engines including Codex and Claude, with optional multi-reviewer panels for high-risk changes. This enables thorough branch diff validation before shipping or merging.

Does automated code review support local dirty changes and single commit reviews?▼

Automated code review supports local dirty change reviews, branch and PR diff reviews, and single commit reviews. This flexible mode coverage ensures both uncommitted local edits and discrete commits pass closeout validation before shipping.

How do I handle security finding suppression during a final code review?▼

During a final code review, security finding suppression is supported with an auditable trail for production-grade code closeout. This ensures accepted findings are verified while non-actionable issues are formally dismissed before release.

Related Skills

Explore More Software Engineering Skills→
xinbenlvxinbenlv
8

retrieve-diff-from-commit

Retrieve unified diffs and commit metadata from local Git repositories.

Community
Intermediate
DuySeuDuySeu
1

gsd-ship

Push verified branches, create PRs, trigger reviews, and track merges on GitHub.

Community
Advanced
jiunbaejiunbae
12

multi-ai-code-review

Coordinate four AI reviewers to analyze code across multiple perspectives.

Community
Advanced
pipecrew-aipipecrew-ai
16

assess

Assess feature branches across repositories for wire-shape agreement and event wiring.

Community
Advanced