skills.rest
zhifengzhang-sz
zhifengzhang-szCOMMUNITY
Explore all skills by this author →
GitHub

review

Analyzes the current PR diff against the base branch for structural, safety, and code-health issues.

Updated Feb 27, 2026
Search Tags:#testing#safety#review#diff#code-quality#pr
One-click install
npx skills add https://github.com/zhifengzhang-sz/divine-book --skill review-zhifengzhang-sz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/zhifengzhang-sz/divine-book/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/zhifengzhang-sz/divine-book --skill review-zhifengzhang-sz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR diffs often contain issues that slip through automated tests. This skill reviews changes before merging to surface safety, reliability, and compatibility concerns.

Core Features & Use Cases

  • Detects potential SQL safety issues, LLM trust boundaries, and structural problems in diffs.
  • Flags missing routing, improves PR quality, ensures code health before landing.
  • Use case: before merging a feature branch, run this review to surface hidden issues that tests might miss.

Quick Start

Analyze the current branch's diff against the base and surface reliability and compatibility concerns before landing.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review PR diffs for SQL safety and code-health issues before merging?▼

To review PR diffs for SQL safety, analyze the current branch changes against the base branch to identify structural issues, potential safety gaps, and code-health problems, returning categorized findings with file references.

What is a pre-landing PR review and when do I need it?▼

A pre-landing PR review is a process that identifies potential safety gaps, LLM trust boundaries, and edge-case coverage issues in your diff before merging, needed when automated tests might miss hidden reliability and compatibility concerns.

How do I catch LLM trust boundary issues and missing routing rules in a feature branch?▼

Catching LLM trust boundary issues and missing routing rules requires running a diff review that scopes for these specific structural problems, flagging them with concrete file references and suggested next steps for fast fixes.

Does this code review skill work without any external dependencies or testing components?▼

This code review skill works without external dependencies or components, analyzing the current branch's diff independently to surface reliability and compatibility concerns directly from the code changes.

What's the best way to surface edge-case coverage problems in a pull request?▼

The best way to surface edge-case coverage problems in a pull request is to analyze the diff against the base branch, identifying missing routing and structural issues to improve PR quality before landing.

Related Skills

Explore More Software Engineering Skills→
jm199seojm199seo

review

Analyze pull request diffs against the base branch for structural issues.

Community
Advanced
TobiasPerryTobiasPerry

review

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

Community
Advanced
chtughachtugha

qa-review

Reviews code changes for test coverage, edge cases, and potential regressions using Python analysis and test generation.

Community
Intermediate
PrirogativusPrirogativus

security-review

Identify and mitigate security vulnerabilities in codebases via static analysis.

Community
Advanced