review

Analyze pull request diffs against the base branch for SQL and LLM safety issues.

55|8|Updated Jul 21, 2021
One-click install
npx skills add https://github.com/Actual-Chat/actual-chat --skill review-actual-chat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Actual-Chat/actual-chat/tree/main/.claude/skills/review
Command: npx skills add https://github.com/Actual-Chat/actual-chat --skill review-actual-chat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR Review automates diff-based analysis against the base branch to detect SQL safety issues, LLM trust boundary violations, and potentially risky side effects before merging.

Core Features & Use Cases

  • Detect base branch for the PR and establish a stable reference for all diff checks.
  • Read and apply a predefined review checklist to ensure comprehensive evaluation.
  • Perform a two-pass review on diffs, including critical safety checks and informational checks, and produce actionable findings.
  • Cross-reference TODOs and summarize findings for PR documentation and decision making.

Quick Start

Trigger the review workflow on a pull request to perform a structured pre-landing review with deterministic steps and detailed guidance.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate pre-landing PR reviews for SQL safety and LLM trust boundary violations?

Pre-landing PR review automation works by detecting the base branch, applying a predefined review checklist, and performing a two-pass diff analysis to produce actionable findings on SQL safety and LLM trust boundaries.

What is the best way to detect conditional side effects in a pull request diff?

Detecting conditional side effects in a pull request diff is handled by a two-pass review that cross-references changes against a predefined checklist to identify potentially risky structural issues and summarize them for PR documentation.

How do I run a deterministic diff analysis on a pull request before merging?

You run a deterministic diff analysis by triggering the review workflow on a pull request, which establishes a stable base branch reference and applies structured safety checks to enable reproducible, auditable reviews.

Does automated PR review work with standard SQL safety checks and prompt handling?

Automated PR review works across codebases involving SQL, data safety checks, and prompt handling, applying critical safety checks and informational checks to surface potential risks early in the diff.

What are the limitations of using a predefined checklist for diff analysis?

Using a predefined checklist for diff analysis limits reviews to deterministic steps and known structural issues like SQL safety and LLM trust boundaries, meaning it may not catch novel risks outside the established checklist scope.