review

Identify structural issues in diffs against the base branch.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/jeisenback/original-curse-killer --skill review-jeisenback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/jeisenback/original-curse-killer/tree/main/.claude/skills/review
Command: npx skills add https://github.com/jeisenback/original-curse-killer --skill review-jeisenback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diff analysis for pre-landing PRs to detect structural issues that tests don't catch, including SQL safety, LLM trust boundary violations, and unintended side effects, helping safer merges.

Core Features & Use Cases

  • Two-pass review workflow: CRITICAL checks on SQL safety, LLM trust, and conditional side effects, followed by INFORMATIONAL checks.
  • Auto-Fix and AskUserQuestion flows to surface concrete actions and decisions during PR review.
  • Greptile triage and design-review-lite support to surface external feedback and frontend design considerations.
  • Comprehensive guidance for pre-landing PR reviews, including plan alignment and escalation when merging.

Quick Start

Run the /review workflow on your branch to start a pre-landing PR assessment and automatically surface fixes and questions.

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 to catch unsafe merges?

Automated pre-landing PR reviews identify structural issues in diffs against the base branch to prevent unsafe merges. The workflow runs a two-pass analysis surfacing SQL data-safety concerns, LLM trust-boundary risks, and conditional side effects before code lands.

What structural issues can automated diff analysis detect before a pull request merge?

Automated diff analysis detects structural issues that tests miss, specifically targeting SQL data-safety concerns, LLM trust-boundary violations, and unintended side effects. It separates critical checks from informational checks to prioritize merge-blocking risks.

How do I start a pre-landing code review on my current branch?

Run the /review workflow on your branch to start a pre-landing PR assessment. The process automatically surfaces concrete auto-fix suggestions and interactive questions to guide necessary fixes and merge decisions.

Does the PR review workflow support auto-fix suggestions for identified code issues?

The PR review workflow supports auto-fix suggestions and an interactive AskUserQuestion flow. These features surface concrete actions and guide decisions directly during the pre-landing review to resolve detected SQL and LLM trust-boundary issues.

What is the best way to review SQL data-safety concerns in a pull request diff?

Reviewing SQL data-safety concerns in a pull request diff is best handled by a two-pass workflow that checks critical structural risks first. This approach surfaces potential data-safety issues and trust-boundary violations before informational checks.

Can I triage external feedback and frontend design considerations during code review?

Triage external feedback and frontend design considerations during code review using integrated Greptile triage and design-review-lite support. This surfaces external feedback and design factors alongside structural diff analysis for safer merges.