review

Name: review
Availability: InStock
Author: andy-hnu

Analyzes PR diffs for SQL safety, LLM trust boundary violations, conditional side effects, and other structural risks.

Updated Mar 9, 2026

Search Tags:#review #diff #static-analysis #ci-cd #pull-request #sql-safety #llm-trust

Ready to run

npx skills add https://github.com/Andy-HNU/AndyClaw --skill review-andy-hnu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Andy-HNU/AndyClaw/tree/main/skills/gstack-review
Command: npx skills add https://github.com/Andy-HNU/AndyClaw --skill review-andy-hnu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when asked to "review this PR", "code review", "pre-landing review", or "check my diff". Proactively suggest when the user is about to merge or land code changes.

Core Features & Use Cases

Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues.
Proactively suggests when the user is about to merge or land code changes.
Use case: When asked to review a PR, surface issues not covered by tests and propose concrete improvements.

Quick Start

Run the review workflow on the current branch to perform a pre-landing PR review.

Frequently Asked Questions about review

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

FAQPage Schema

How do I perform an automated pre-landing code review on my pull request diff?▼

Pre-landing PR review analyzes your current branch diff against the base branch to identify SQL safety issues, LLM trust boundary violations, and conditional side effects before you merge changes.

What structural risks does an automated code review check for in a pull request?▼

Automated PR review checks for SQL safety issues, LLM trust boundary violations, conditional side effects, and other structural risks by applying a two-pass analysis to surface issues and propose concrete fixes.

How do I check my diff for SQL safety and LLM trust boundary violations before merging?▼

Checking your diff involves loading deterministic checks and context from the PR diff to identify SQL safety issues and LLM trust boundary violations, escalating issues if needed with a deterministic remediation plan.

Can I use static analysis to surface issues not covered by tests in my pre-landing review?▼

Static analysis in pre-landing review surfaces structural issues not covered by tests, applying a two-pass review process to propose concrete improvements and escalate risks before code changes land.

Does automated pull request review work without external dependencies or CI-CD integrations?▼

Automated pull request review operates with no external dependencies, loading deterministic checks directly from the PR diff to guide actions and maintain safety during the pre-landing workflow.

When should I run a pre-landing review on my branch before merging code changes?▼

Pre-landing review should run when you are about to merge or land code changes, analyzing the branch diff against the base branch to catch structural risks and propose fixes before landing.