review

Analyze diffs against the base branch to surface structural issues.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/fray-cloud/coin --skill review-fray-cloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/fray-cloud/coin/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/fray-cloud/coin --skill review-fray-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes diffs against the base branch to surface structural issues that tests alone may miss, helping teams catch risks before merging.

Core Features & Use Cases

  • Pre-landing PR review to surface SQL safety concerns, LLM trust boundary violations, and conditional side effects.
  • Automated guidance for code reviews, highlighting potential design and quality gaps that tests won't cover.
  • Works across repositories and workflows to streamline the review process and improve merge quality.

Quick Start

Run the review workflow on your current branch to surface structural issues before merging.

Frequently Asked Questions about review

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

FAQPage Schema
How do I detect SQL safety issues in a pre-landing PR review?

Pre-landing PR review detects SQL safety issues by analyzing branch diffs against the base branch to surface structural risks before merging. It flags potential injection points and unsafe query patterns that standard tests may miss.

What structural issues can diff analysis find that tests miss?

Diff analysis finds structural issues like LLM trust boundary violations, conditional side effects, and scope drift that tests miss. It analyzes code changes to highlight design gaps and potential risks before landing the merge.

Does plan mode work with automated diff analysis for scope drift detection?

Yes, plan mode works with automated diff analysis to detect scope drift during pre-landing code reviews. It evaluates branch changes to ensure modifications align with the intended design before merging.

How do I extract actionable items from a PR diff before merging?

You extract actionable items from a PR diff by running the review workflow on your current branch. It analyzes changes against the base branch to generate specific guidance for code reviews and improve merge quality.

Can I use telemetry logging to track pre-landing code review results?

Yes, you can use telemetry logging to track pre-landing code review results. The review workflow supports telemetry logging alongside diff analysis to monitor structural issues like SQL safety concerns and conditional side effects.

What are the limitations of automated code review for LLM trust boundaries?

Automated code review for LLM trust boundaries focuses on surfacing structural issues in diffs but may not catch all complex runtime behaviors. It is designed to flag potential trust boundary violations rather than fully enforce them.