review

Analyze feature branch diffs for SQL safety and LLM trust boundary issues.

4|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/lendtrain/complete-pipeline --skill review-lendtrain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/lendtrain/complete-pipeline/tree/main/skills/review
Command: npx skills add https://github.com/lendtrain/complete-pipeline --skill review-lendtrain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR review helps catch SQL safety issues, LLM trust boundary violations, and structural concerns before merging, reducing production risk.

Core Features & Use Cases

  • Analyzes diffs against base branches for security, correctness, and maintainability.
  • Provides actionable findings and recommended remediations for fast fixes.
  • Proactively flags risks during code review and PR landings.

Quick Start

Invoke the /review workflow on the current branch to start 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 run a pre-landing PR review on my feature branch?

Pre-landing PR review analyzes the diff between your feature and base branches to identify SQL safety issues, LLM trust boundary violations, and structural problems before merging. Invoke the review workflow on your active branch to generate actionable findings and remediation guidance.

What does diff-based code review check for before merging?

Diff-based code review checks for SQL safety issues, LLM trust boundary violations, and potential structural problems. It evaluates changes touching databases, prompts, or critical logic to classify findings and provide precise checklists for safe landings.

Can I use automated PR review to catch SQL safety issues in database changes?

Yes, automated PR review specifically catches SQL safety issues by analyzing diffs against base branches. It flags risks in changes touching databases and provides recommended remediations to ensure safe code landings.

How do I check for LLM trust boundary violations in my code?

Checking for LLM trust boundary violations involves analyzing your diff for prompt and critical logic changes. The review process flags these violations during pre-landing assessment and provides actionable remediation guidance to secure your LLM integrations.

When do I need a pre-landing review for my pull request?

You need a pre-landing review when your pull request touches databases, prompts, or critical logic. It proactively flags security, correctness, and maintainability risks before merging, reducing production risk by surfacing precise guidance for safe landings.

What is the best way to analyze diffs for structural problems before a merge?

The best way to analyze diffs for structural problems is using an automated pre-landing review workflow. It classifies findings from the feature branch diff, provides actionable remediation steps, and ensures code correctness and maintainability before production landing.