review

Analyze branch diffs against origin/main for merge safety issues.

2|Updated Dec 8, 2018
One-click install
npx skills add https://github.com/indykish/dotfiles --skill review-indykish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/indykish/dotfiles/tree/main/skills/review
Command: npx skills add https://github.com/indykish/dotfiles --skill review-indykish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes diffs between the current branch and origin/main to surface structural issues that tests don't catch, enabling safer merges.

Core Features & Use Cases

  • Two-pass review workflow: CRITICAL pass for SQL/data safety and LLM trust, and INFORMATIONAL pass for broader checks.
  • Output comprehensive findings in a consistent format, with optional prompts for critical issues.
  • Works on local diffs and PR workflows to prevent unsafe changes from being merged.

Quick Start

Run the /review workflow to analyze the current branch’s diff against origin/main for structural issues.

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 safe merges?

Automating pre-landing PR reviews involves running a workflow that identifies diffs between your current branch and origin/main. This surfaces structural merge safety issues across SQL safety, LLM trust boundaries, and consistency, generating a structured findings report.

What structural issues should a PR diff checklist catch before merging?

A PR diff checklist should catch critical SQL safety and LLM trust boundary issues, alongside broader informational consistency findings. Identifying these structural problems before merging prevents unsafe code changes from landing in the main branch.

How does a two-pass review workflow work for git diffs?

A two-pass review workflow applies a checklist to git diffs in stages. The first pass surfaces CRITICAL issues affecting SQL and LLM trust, while the second pass generates INFORMATIONAL findings for broader consistency checks.

Can I review local git diffs against origin/main without pushing?

Yes, you can review local git diffs against origin/main without pushing. The workflow analyzes local branch differences directly, producing a comprehensive findings report to ensure merge safety before code is published.

What is an LLM trust boundary in code review?

An LLM trust boundary in code review defines where untrusted LLM outputs interact with system logic or data. Reviewing diffs for this boundary ensures SQL safety and prevents unintended model behavior from causing critical merge issues.

Does automated PR review work for both local diffs and remote PR workflows?

Automated PR review works for both local diffs and remote PR workflows. It analyzes differences between the current branch and origin/main to prevent unsafe changes from merging, providing consistent structural safety checks across environments.