skills.rest
lachieh
lachiehCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

review

Analyze diffs against the base branch for SQL safety and trust boundary issues.

Updated Mar 15, 2026
Search Tags:#code-review#pr-review#diff-analysis#sql-safety#llm-trust#pre-landing
One-click install
npx skills add https://github.com/lachieh/babytalk --skill review-lachieh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/lachieh/babytalk/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/lachieh/babytalk --skill review-lachieh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review and ensure pull requests are structurally safe by analyzing diffs against the base branch for SQL safety, LLM trust boundaries, conditional side effects, and other structural issues that can emerge during merging. It helps teams catch issues early before landing changes.

Core Features & Use Cases

  • Detects drift between the PR and its stated intent, names potential scope gaps, and surfaces actionable questions to clarify before merge.
  • Flags SQL safety concerns, LLM trust boundary violations, and conditional side effects that might alter behavior or data integrity.
  • Provides proactive remediation guidance and a ready-to-discuss checklist for reviewers and authors.

Quick Start

Run a pre-landing PR review on the current branch to inspect the diff against the base branch and surface blockers.

Frequently Asked Questions about review

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

FAQPage Schema
How do I catch SQL safety issues in a pull request before merging?▼

Pre-landing PR review detects LLM trust boundary violations by analyzing diffs against the base branch. It flags conditional side effects and trust boundary issues that might alter behavior, ensuring structural safety before changes land.

How do I check for scope drift between a pull request and its stated intent?▼

To check for scope drift between a pull request and its stated intent, analyze the PR diff alongside its stated goals. This detects potential scope gaps and surfaces actionable questions to clarify discrepancies before merge.

What is the best way to automate pre-landing validation for structural code issues?▼

The best way to automate pre-landing validation for structural code issues is running a diff analysis against the base branch. It proactively surfaces SQL safety concerns, LLM trust boundary violations, and conditional side effects before landing.

Can I use diff analysis to generate a reviewer checklist for PR checks?▼

Yes, you can use diff analysis to generate a reviewer checklist for PR checks. It analyzes PR intent, TODOS, and diff context to produce a ready-to-discuss checklist with proactive remediation suggestions for reviewers and authors.

Does pre-landing review work for detecting conditional side effects in a diff?▼

Pre-landing review works for detecting conditional side effects by analyzing the diff against the base branch. It identifies structural issues and behavioral alterations caused by conditional logic before the code merges.

Related Skills

Explore More Software Engineering Skills→
detorresramosdetorresramos
3

catching-up

Summarize current branch code changes relative to the base branch.

Community
Intermediate
ksciuskscius
2

fix-merge-conflicts

Resolve Git merge conflicts and verify buildable, test-passing state.

Community
Advanced
meistro57meistro57
1

laravel:quality-checks

Run automated quality gates for Laravel projects with Pint, PHPStan, and frontend linters.

Community
Intermediate
R2W1csR2W1cs
1

lint-and-validate

Lint and validate JavaScript and Python code for syntax and style issues.

Community
Intermediate