review

Analyze PR diffs for SQL safety, trust boundaries, and side effects.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/onlypfachi/chief --skill review-onlypfachi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/onlypfachi/chief/tree/main/review
Command: npx skills add https://github.com/onlypfachi/chief --skill review-onlypfachi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR reviews are often error-prone, missing structural issues, and failing to enforce safety boundaries. This Skill analyzes the diff against the base branch to surface SQL safety concerns, potential LLM trust violations, and unintended conditional side effects, enabling safer merges.

Core Features & Use Cases

  • Analyzes diffs for SQL safety, trust boundaries, and conditional side effects.
  • Performs a two-pass review (critical then informational) and proposes auto-fixes or asks for input.
  • Generates precise file references and a plan to improve PR readiness before landing.

Quick Start

Provide the PR diff and base branch context to trigger a structured pre-landing review.

Frequently Asked Questions about review

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

FAQPage Schema
How do I analyze a PR diff for SQL safety and LLM trust boundary violations?

To analyze a PR diff for SQL safety and LLM trust boundaries, you provide the PR diff and base branch context to trigger a structured pre-landing review. The Skill evaluates the changes to identify trust violations, SQL risks, and conditional side effects before merging.

What is a pre-landing PR review and how does it detect unintended side effects?

A pre-landing PR review evaluates code changes against a base branch before merging to detect unintended conditional side effects. This process surfaces structural issues, scope drift, and missing requirements to ensure code readiness and enforce safety boundaries.

Can I automatically generate fixes for scope drift and missing requirements in a pull request?

Yes, you can automatically generate fixes for scope drift and missing requirements. The review performs a two-pass analysis, proposing complete auto-fixes or prompting for input via a structured AskUserQuestion flow to guide safer merges.

Does this automated code review tool require any specific dependencies or components?

No, this automated code review tool requires no external dependencies or components. You simply provide the PR diff and base branch context to trigger the structured pre-landing review process directly.

What is the best way to surface actionable findings with precise file references before merging?

The best way to surface actionable findings with precise file references is to run a two-pass pre-landing review. It evaluates critical and informational issues, providing exact file locations and a plan to improve PR readiness before landing.