skills.rest
bhianerd
bhianerdCOMMUNITY
Explore all skills by this author →
GitHub

review

Review pull request diffs for SQL safety, LLM trust boundaries, and concurrency hazards.

1|Updated Mar 25, 2026
Search Tags:#diff analysis#code review#concurrency#SQL injection#pre-merge safety#LLM trust boundary
One-click install
npx skills add https://github.com/bhianerd/aimemory --skill review-bhianerd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/bhianerd/aimemory/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/bhianerd/aimemory --skill review-bhianerd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you avoid risky SQL, unsafe LLM-driven behavior, and other structural issues before you merge code, so you don’t ship problems that tests might miss.

Core Features & Use Cases

  • Diff-focused safety review: Analyzes changes against the base branch for SQL safety, LLM trust-boundary violations, conditional side effects, and concurrency/race-condition hazards.
  • Two-pass checking: Runs critical checks first, then informational checks to catch smaller but still meaningful problems.
  • Design review when frontend is touched: Adds a lightweight UI/UX pass for changed frontend files when applicable.
  • Optional Greptile triage: Incorporates prior line-level comments when available to reduce duplicate work and support escalation detection.

Quick Start

Ask your agent to run /review when you want a pre-landing review of a PR diff (for example, when you say “review this PR” or “check my diff”).

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a PR diff for SQL injection and concurrency hazards before merge?▼

Reviewing a PR diff for SQL injection and concurrency hazards involves fetching the base branch diff, applying a review checklist, and running a two-pass analysis to proactively catch critical safety issues before merging.

What is a pre-landing code review and when do I need it?▼

Pre-landing code review is a pre-flight validation process that analyzes a pull request diff against the base branch to catch structural correctness issues, LLM trust boundary violations, and conditional side effects before code merge.

How do I check my diff for LLM trust boundary violations and race conditions?▼

Checking a diff for LLM trust boundary violations and race conditions requires a two-pass analysis: the first pass targets critical safety issues, while the second addresses informational checks for structural completeness across consumers.

Can I use a code review checklist to catch conditional side effects in frontend changes?▼

Yes, applying a review checklist to PR diffs catches conditional side effects, and when frontend files are touched, it automatically adds a lightweight UI/UX design review pass to ensure structural correctness.

Does pre-merge safety review work with Greptile for line-level triage?▼

Pre-merge safety review optionally incorporates Greptile triage by fetching prior line-level comments, reducing duplicate review work and supporting escalation detection during the diff analysis.

Related Skills

Explore More Software Engineering Skills→
AkbarDevopAkbarDevop

review

Identify production-risk findings in a code diff before merging.

Community
Advanced
antriksh-29antriksh-29

review

Analyzes diffs for SQL safety, LLM trust boundary violations, and side effects pre-merge.

Community
Advanced
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced
hightemphightemp

aif-security-checklist

Provides a complete security audit of your project, including advanced checks.

Community
Advanced