git-review

Name: git-review
Availability: InStock
Author: olliecrow

Review a Git branch against main for critical issues and regressions.

Updated Aug 23, 2026

Search Tags:#git #code review #security audit #regression testing #merge readiness #branch analysis

Ready to run

npx skills add https://github.com/olliecrow/codex --skill git-review-olliecrow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-review
Source: https://github.com/olliecrow/codex/tree/main/skills/git-review
Command: npx skills add https://github.com/olliecrow/codex --skill git-review-olliecrow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the rigorous review of code changes against a main branch, identifying critical issues and ensuring code quality before merging.

Core Features & Use Cases

Comprehensive Branch Auditing: Analyzes all changes on a feature branch against the main branch for correctness, security, and regressions.
Severity-First Findings: Prioritizes and reports evidence-backed critical red flags and serious issues.
Use Case: Before merging a new feature, use this Skill to perform a deep audit, ensuring no critical bugs or security vulnerabilities are introduced, and confirming the code is ready for production.

Quick Start

Use the git-review skill to perform a full branch review against main.

Frequently Asked Questions about git-review

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

FAQPage Schema

How do I automate a code review for a git branch before merging?▼

To automate a code review before merging, you can audit a feature branch against the main branch to identify critical red flags, security vulnerabilities, and regressions. This process operates autonomously to ensure merge readiness.

What is a severity-first code review and how does it work?▼

A severity-first code review prioritizes reporting the most critical issues and serious regressions before minor ones. It analyzes branch changes against main, presenting evidence-backed findings to ensure high-risk problems are addressed first.

Can I run a security audit on a specific scope of my git branch?▼

Yes, you can run a security audit on a specific scope of your git branch. The review supports scoped analysis for specific areas, allowing you to target checks rather than reviewing the entire branch diff.

Does the code review process require manual input for fixing and committing changes?▼

The code review process requires explicit user input only for high-risk actions. It features integrated closeout modes that autonomously fix, verify, and commit changes after identifying critical issues during the audit.

When do I need a deep branch analysis before a production merge?▼

You need a deep branch analysis before a production merge to ensure no critical bugs or security vulnerabilities are introduced. It confirms code readiness by auditing correctness and regressions against the main branch.