skills.rest
JovieInc
JovieIncOFFICIAL
Explore all skills by this author →
WebsiteGitHub

review

Analyzes the current branch diff for SQL safety, LLM trust boundary violations, and conditional side effects before merging.

Updated Aug 2, 2025
Search Tags:#automation#review#diff#pull-request#pr-check
One-click install
npx skills add https://github.com/JovieInc/Jovie --skill review-jovieinc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/JovieInc/Jovie/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/JovieInc/Jovie --skill review-jovieinc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Pre-landing PR review automates the analysis of diffs against the base branch to surface structural issues not caught by tests, enabling safer merges and higher code quality.

Core Features & Use Cases

  • Two-pass review workflow that prioritizes SQL safety, LLM trust boundaries, and conditional side effects.
  • Stepwise checks including branch status, diff retrieval, and a formal TODO/goals alignment with PR intent.
  • Telemetry and session logging to track outcomes for continuous improvement.

Quick Start

Run the pre-landing PR review workflow on your PR to scan the diff and surface actionable findings before merging.

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 review to catch SQL safety issues before merging?▼

Automated pre-landing PR review analyzes your branch diff against the base branch to identify SQL safety issues. It runs a two-pass workflow to surface structural problems not caught by tests, enabling safer merges.

What is a two-pass diff analysis workflow for pull requests?▼

A two-pass diff analysis workflow systematically reviews pull request diffs by first checking branch status and retrieving diffs, then consulting a formal checklist to align PR intent with goals. This process prioritizes SQL safety, LLM trust boundaries, and conditional side effects.

Can I use automated code review to detect LLM trust boundary violations in my diff?▼

Yes, you can use automated code review to detect LLM trust boundary violations in your diff. The review process specifically targets these violations alongside conditional side effects that could affect a merge, ensuring structural integrity.

Does automated PR review work without external dependencies for check-my-diff workflows?▼

Yes, automated PR review works without external dependencies for check-my-diff workflows. It operates independently using internal scripts and references to analyze diffs and log telemetry outcomes across repositories.

What's the best way to check my diff for conditional side effects before a merge?▼

The best way to check your diff for conditional side effects is running an automated pre-landing review. It evaluates the current branch diff against the base branch, enforcing a stepwise check to identify side effects that could affect a merge.

Related Skills

Explore More Software Engineering Skills→
jm199seojm199seo

review

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

Community
Advanced
JoviDeCroockJoviDeCroock
29

session-lessons

Analyze Pi session JSONL logs to detect repeated assistant errors.

Community
Intermediate
NoobyGainsNoobyGains
78

quality-enforcement

Enforce code quality standards across pre-commit, pre-merge, and CI pipeline stages.

Community
Advanced
RedHatProductSecurityRedHatProductSecurity
47

semgrep

Automate static code analysis for security vulnerabilities across multi-language repositories.

Official
Intermediate