review

Automate git diff reviews on staging branches for merge or reject decisions.

Updated Feb 18, 2026

Search Tags:#automation #git #code review #merge #staging branch #reject

Ready to run

npx skills add https://github.com/ollieb89/openrepo --skill review-ollieb89

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the code review process by automating the analysis of git diffs on staging branches, enabling quick merge or reject decisions to maintain code quality and architectural consistency.

Core Features & Use Cases

Automated Code Review: Analyzes code quality, architecture, security, performance, and testing adherence.
Merge/Reject Decisions: Automatically merges approved changes or rejects those with clear feedback.
Use Case: After an L3 specialist pushes code to a feature branch, this skill can be invoked to perform an initial review, merging it if it meets all criteria or rejecting it with specific reasons if it violates architectural guidelines.

Quick Start

Use the review skill to review the staging branch 'feature/new-api' for task 'task-001' and merge the changes.

Frequently Asked Questions about review

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

FAQPage Schema

How do I automate code review for git diffs on a staging branch?▼

Automated code review analyzes git diffs on staging branches to assess code quality, architecture, security, performance, and testing adherence. It then provides automatic merge or reject decisions based on predefined project criteria.

Can I automatically reject code changes that violate architectural guidelines?▼

Yes, automated code review can reject code changes that violate architectural guidelines. When a staging branch diff fails the assessment against predefined criteria, the changes are rejected with specific, clear feedback detailing the violations.

How do I automatically merge approved feature branch changes?▼

To automatically merge approved feature branch changes, an automated review process evaluates the git diff against code quality and architectural criteria. If the changes meet all predefined standards, the merge is executed automatically.

What does automated code quality assessment check in a git diff?▼

Automated code quality assessment checks a git diff for code quality, architecture, security, performance, and testing adherence. This ensures code pushed to staging branches maintains architectural consistency and meets predefined project standards.

Does automated code review require integration with project state tracking systems?▼

Yes, automated code review requires integration with project state tracking systems. This integration facilitates accurate diff analysis and ensures merge or reject decisions align with the predefined criteria and current task context.

When should I use automated merge and reject decisions for staging branches?▼

Use automated merge and reject decisions for staging branches when performing L3 work that requires strict code quality assurance. It streamlines the review process by automatically enforcing architectural consistency before changes are merged.