review

Name: review
Availability: InStock
Author: Akbar

Identify production-risk findings in a code diff before merging.

Updated Mar 12, 2026

Search Tags:#automation #checklist #review #diff #code-quality #risk-assessment #pre-landing

Ready to run

npx skills add https://github.com/AkbarDevop/gstack-codex --skill review-akbardevop

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-Landing Review helps teams detect and fix critical issues in a diff before merging, reducing risk and rework downstream.

Core Features & Use Cases

Atomic two-pass review prioritizes critical issues (SQL/data safety, race conditions, and LLM output trust) and surfaces actionable improvements.
Reads the diff against the repository default branch, fetches the full changes, and outputs a structured findings report for PR discussions.
Use Case: When preparing a feature branch for merge, run this skill to surface potential production risks and guidance for remediation.

Quick Start

Run the pre-landing review on your current branch diff to generate a concise risk report.

Frequently Asked Questions about review

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

FAQPage Schema

What is a pre-landing code review and when do I need it?▼

A pre-landing code review identifies production risks in a diff before merging. You need it when preparing a feature branch to catch critical issues like SQL/data safety and race conditions early, reducing downstream rework.

How do I run a pre-landing review on my current branch diff?▼

Run the review skill on your current branch to extract the diff against the default branch. It fetches full changes and performs a two-pass critique using a checklist to output a structured findings report.

What specific production risks does the code review checklist look for?▼

The code review checklist prioritizes critical production risks including SQL and data safety issues, race conditions, and untrusted LLM output handling, flagging them first to provide concise remediation fixes.

Can I use this review skill on diffs against any branch?▼

Apply this review skill to diffs against the repository default branch. It resolves the base branch, extracts the diff, and performs a two-pass critique to generate structured risk findings for PR discussions.

How does the two-pass critique mechanism work for code quality assessment?▼

The two-pass critique mechanism analyzes a code diff by first prioritizing critical issues like data safety and race conditions, then surfacing actionable improvements to generate a structured code quality risk report.