review

Analyzes a Git branch against main for SQL safety, race conditions, and more.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/xuithoi/Claudecode_gtask --skill review-xuithoi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/xuithoi/Claudecode_gtask/tree/main/review
Command: npx skills add https://github.com/xuithoi/Claudecode_gtask --skill review-xuithoi

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of reviewing code changes before they are merged into the main branch, catching critical issues that automated tests might miss.

Core Features & Use Cases

  • Structural Issue Detection: Analyzes code diffs for SQL safety, LLM trust boundary violations, race conditions, and other complex bugs.
  • Checklist-Driven Review: Follows a comprehensive checklist to ensure all critical areas are examined.
  • Use Case: Before merging a new feature, run /review to get an automated, in-depth analysis of potential bugs, security vulnerabilities, and architectural flaws, ensuring higher code quality and stability.

Quick Start

Run the review skill to analyze the current branch's changes against main.

Frequently Asked Questions about review

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

FAQPage Schema
What is pre-landing code review and how does it detect race conditions in a Git branch?

Pre-landing code review is an automated analysis of a Git branch against main to detect structural issues like race conditions before merging. It uses a comprehensive checklist to examine code diffs for complex bugs and security vulnerabilities.

How do I review a Git branch for SQL safety and LLM trust boundary violations before merging?

You can review a Git branch for SQL safety and LLM trust boundary violations by running an automated pre-landing review against the main branch. This identifies critical structural issues and provides actionable feedback for developers to address before merging.

Can I catch enum or value completeness issues that automated tests might miss?

Yes, you can catch enum and value completeness issues through checklist-driven pre-landing code review. This automated process analyzes code diffs to identify critical structural problems that standard automated tests often miss before the branch merges.

Does a checklist-driven PR review work without additional dependencies?

Yes, checklist-driven PR review works without additional dependencies. It operates directly on your Git branch changes against main, requiring no external packages to identify SQL safety issues, race conditions, and architectural flaws.

What's the best way to ensure code quality and stability before merging a new feature?

The best way to ensure code quality before merging a new feature is running an in-depth pre-landing code review. This analyzes potential bugs, security vulnerabilities, and architectural flaws using a detailed checklist, ensuring higher stability.

When should I not rely on automated PR review for debugging critical structural issues?

You should not rely solely on automated PR review when debugging requires runtime analysis or complex business logic validation. Pre-landing review focuses on structural issues like SQL safety and race conditions found in static code diffs.