review

Analyze git diffs against the main branch for structural, security, and logic defects.

1|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/gth-ai/hadriengayap.github.io --skill review-gth-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/gth-ai/hadriengayap.github.io/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/gth-ai/hadriengayap.github.io --skill review-gth-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies structural issues, security vulnerabilities, and logic errors in code changes that standard automated tests often overlook.

Core Features & Use Cases

  • Critical Safety Checks: Detects SQL injection risks, race conditions, and LLM trust boundary violations.
  • Informational Audits: Flags magic numbers, dead code, and inconsistent documentation to maintain high code quality.
  • Use Case: Before merging a pull request, run this review to ensure that new database queries are properly sanitized and that no sensitive data is being exposed through improper LLM output handling.

Quick Start

Run the review skill to analyze the current branch against the main branch for potential structural and security issues.

Frequently Asked Questions about review

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

FAQPage Schema
How do I detect SQL injection risks in a git pull request?

To detect SQL injection risks in a pull request, you can use automated static analysis to evaluate git diffs against the main branch. This process identifies unparameterized database queries and other structural security defects before merging.

What is the best way to check LLM trust boundaries before merging code?

Checking LLM trust boundaries before merging code involves analyzing git diffs for improper output handling that exposes sensitive data. Automated code review flags these violations to ensure new logic respects established security perimeters.

Can automated code review identify race conditions in my git diff?

Automated code review can identify race conditions in a git diff by applying a two-pass static analysis process. It targets concurrency issues alongside SQL safety and structural defects to provide pre-landing quality assurance.

How do I flag dead code and magic numbers in pull requests?

To flag dead code and magic numbers in pull requests, run an informational audit on your git branch changes. This static analysis detects inconsistent documentation and structural logic errors to maintain high code quality.

Do I need automated tests to find logic errors that standard tests overlook?

You do not need automated tests to find logic errors that standard tests overlook. A dedicated static analysis tool can review git diffs for structural issues and security vulnerabilities, identifying overlooked defects without executing test suites.