review

Analyze pull request diffs for SQL safety, LLM trust boundary violations, and side effects.

1|1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/nuurpro/Converza_ai --skill review-nuurpro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/nuurpro/Converza_ai/tree/main/.claude/skills/review
Command: npx skills add https://github.com/nuurpro/Converza_ai --skill review-nuurpro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines pre-landing PR reviews by automatically analyzing code diffs for structural issues that tests often miss, including SQL safety, LLM trust boundary violations, and unintended side effects.

Core Features & Use Cases

  • Diff analysis for SQL safety, conditional side effects, and other structural issues that may slip past tests.
  • LLM trust boundary checks to catch prompt injection, data exposure, and other trust boundary violations in PR content.
  • Plan drift and TODOS alignment validation to ensure the PR delivers exactly what was requested.
  • Proactive recommendations for reviewer actions and potential merge-time risks.

Quick Start

Provide a pre-landing PR review on the current diff to surface issues and suggested fixes.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate pull request review for SQL safety and side effects?

Automated pull request review analyzes code diffs to detect SQL safety issues, unintended side effects, and LLM trust boundary violations that test suites often miss. It compares the diff against the base branch to surface actionable findings before merge.

What issues does pre-landing code diff analysis catch that tests miss?

Pre-landing code diff analysis catches structural issues tests miss, including SQL safety problems, LLM trust boundary violations, conditional side effects, and plan drift. It verifies adherence to TODOS and PR descriptions to ensure the PR delivers exactly what was requested.

How do I check a pull request for LLM trust boundary violations?

Checking a pull request for LLM trust boundary violations involves analyzing the PR diff for prompt injection risks, data exposure, and other trust issues. The review operates with configured toolsets to surface these vulnerabilities alongside standard code safety findings.

Can I validate PR scope drift and plan alignment from a git diff?

You can validate PR scope drift and plan alignment by comparing the git diff against the base branch. The review verifies the changes match plan items, TODOS, and PR descriptions, surfacing any drift to ensure the code delivers exactly what was requested.

What is the best way to review code diffs for unintended side effects?

Reviewing code diffs for unintended side effects is best handled by automated pre-landing analysis that checks conditional logic and structural changes in the pull request. This approach identifies potential merge-time risks and provides proactive recommendations for reviewers.

Does automated PR review work without external dependencies?

Automated PR review works without external dependencies, operating with your configured toolset and plan context to analyze diffs. It functions independently to surface actionable findings, plan-ahead recommendations, and potential blockers directly from the base branch comparison.