review

Name: review
Availability: InStock
Author: VanL

Analyze code diffs for security vulnerabilities, concurrency bugs, and quality issues.

1|Updated Jul 6, 2025

Search Tags:#code quality #diff analysis #code review #security #SQL safety

Ready to run

npx skills add https://github.com/VanL/simplebroker --skill review-vanl

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/VanL/simplebroker/tree/main/.agents/skills/gstack/review
Command: npx skills add https://github.com/VanL/simplebroker --skill review-vanl

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers analyze pull request diffs to identify structural issues, SQL safety violations, and trust boundary problems before merging code.

Core Features & Use Cases

Diff Analysis: Automatically reviews code differences for security, correctness, and structural issues.
Structural Review: Checks for SQL injection, race conditions, and unsafe code patterns in the codebase.
Use Case: When preparing a PR, use this Skill to ensure the code is safe, reliable, and aligns with best practices, avoiding costly regressions.

Quick Start

Ask the AI to review recent code changes in the repository before merging to catch issues early.

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 SQL injection and security vulnerabilities before merging a pull request?▼

Code diff analysis detects SQL injection and security vulnerabilities by parsing pull request differences and applying static code analysis to identify unsafe patterns before merging. It proactively checks trust boundaries to mitigate risk in software engineering projects.

What is pre-landing code review for trust boundaries and race conditions?▼

Pre-landing code review is the process of evaluating structural changes in a pull request to identify race conditions, concurrency bugs, and trust boundary problems. It ensures code reliability and aligns with pre-release quality standards before integration.

Can I use automated diff analysis to check for unsafe code patterns in my software engineering workflow?▼

Yes, automated diff analysis evaluates code differences in your software engineering workflow to check for unsafe code patterns. It applies pattern matching for safety violations and concurrency bugs, ensuring proactive quality assurance and risk mitigation.

How do I review recent code changes in a repository to catch structural issues early?▼

To review recent code changes, request an analysis of the repository diff to catch structural issues early. The system parses the diff output and applies static code analysis to detect potential security vulnerabilities and code quality issues.

What are the limitations of static code analysis for detecting concurrency bugs in pull requests?▼

Static code analysis limitations include relying on pattern matching for diff outputs to detect concurrency bugs, which may miss complex runtime-specific race conditions. It focuses on structural review and known unsafe code patterns rather than dynamic execution tracing.