skills.rest
jm199seo
jm199seoCOMMUNITY
Explore all skills by this author →
GitHub

review

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

Updated Mar 22, 2026
Search Tags:#review#diff#code-quality#static-analysis#pull-request#pr-checklist
One-click install
npx skills add https://github.com/jm199seo/lostark-accessory-viewer --skill review-jm199seo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/jm199seo/lostark-accessory-viewer/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/jm199seo/lostark-accessory-viewer --skill review-jm199seo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR reviews often miss subtle issues in diffs against the base branch, leading to faulty merges and unstable releases. This guide helps you systematically detect SQL safety concerns, trust boundary violations, and intent mismatches before landing code.

Core Features & Use Cases

  • Structured two-pass diff analysis for safety, quality, and scope adherence.
  • Generates actionable findings (AUTO-FIX or ASK) following the Fix-First approach.
  • Integrates with standard PR workflows to surface issues early and reduce merge risks.

Quick Start

Run this skill on the current PR branch to scan the diff against the base and surface critical 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 analyze a pull request diff for code quality and safety risks?▼

To analyze a pull request diff for code quality and safety risks, run a structured two-pass review against the base branch to detect SQL safety concerns, trust boundary violations, and intent mismatches before merging.

What is the best way to automate static analysis for a PR checklist?▼

Automating static analysis for a PR checklist involves scanning the current branch diff to surface structural issues and generate actionable findings like AUTO-FIX or ASK suggestions, integrating directly with standard PR workflows.

How does diff analysis identify trust boundary violations in a pull request?▼

Diff analysis identifies trust boundary violations in a pull request by comparing the current branch changes against the base branch to systematically detect safety concerns and scope deviations across the modified code.

Can I use this structured review process on an existing repository base branch?▼

Yes, you can use this structured review process on an existing repository base branch, provided you have repository access and tools for diff analysis and PR inspection to evaluate the current changes.

What types of findings does a structured PR review generate for faulty merges?▼

A structured PR review generates actionable findings for faulty merges by outputting AUTO-FIX or ASK directives following a Fix-First approach, targeting code quality checks and potential safety risks.

When do I need to run a structured PR review before landing code?▼

You need to run a structured PR review before landing code when you want to systematically detect structural issues, safety risks, and scope adherence problems in the diff to prevent unstable releases.

Related Skills

Explore More Software Engineering Skills→
huichenhuichen

review

Analyze branch diffs for structural issues and classify plan items.

Community
Advanced
coco-researchcoco-research
264

gsd-ship

Push a verified branch and create a merge-ready pull request.

Community
Advanced
SensLiaoSensLiao

qa-static-baseline

Automate static code analysis and security scanning on pull requests or CI pipelines.

Community
Intermediate
smarmen86smarmen86

review

Analyze git diffs against base branches for SQL vulnerabilities and code defects.

Community
Advanced