review

Analyze code diffs for security, correctness, and structural integrity.

2|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/esopian/blue-oak-audit --skill review-esopian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/esopian/blue-oak-audit/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/esopian/blue-oak-audit --skill review-esopian

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers analyze pull requests for structural and security issues, ensuring code quality before landing.

Core Features & Use Cases

  • Diff Analysis: Examines code changes against best practices for SQL safety, concurrency, and trust boundary violations.
  • Structural Checks: Detects potential race conditions, unsafe HTML, and enum inconsistencies that could cause bugs.
  • Use Case: When reviewing a PR with 500 lines changed, it highlights potential security vulnerabilities, data issues, and structural risks to prevent production bugs.

Quick Start

Provide the diff of your PR to the review system to automatically analyze and receive a detailed report of issues.

Frequently Asked Questions about review

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

FAQPage Schema
How do I analyze code diffs for security and structural issues before merge?

To analyze code diffs for security and structural issues, provide your pull request diff to the review system to automatically check SQL queries, concurrency, and trust boundaries, yielding a detailed report of vulnerabilities before merge.

What is a trust boundary violation in code review?

A trust boundary violation in code review occurs when untrusted data crosses into trusted segments without validation. This structural check detects unsafe HTML and potential race conditions within pull requests to prevent security vulnerabilities.

How do I check SQL queries and enum safety in a pull request?

To check SQL queries and enum safety in a pull request, submit the code diff for automated analysis. The system validates SQL safety and detects enum inconsistencies, returning a structural integrity report to prevent bugs.

Can I use automated code review for large diffs with 500 lines changed?

Yes, you can use automated code review for large diffs with 500 lines changed. The system highlights potential security vulnerabilities, data issues, and structural risks across the entire diff to prevent production bugs.

Does this structural analysis detect race conditions and concurrency issues?

Yes, this structural analysis detects race conditions and concurrency issues. It examines code changes against best practices for concurrency, ensuring structural integrity and preventing potential bugs before landing code.

When do I need pre-landing PR review for SQL safety?

You need pre-landing PR review for SQL safety when your code changes involve database queries or trust boundaries. It ensures structural integrity and prevents data issues before the code merges into production.