skills.rest
madebynoam
madebynoamCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

review

Analyze PR diffs against main for SQL safety and trust boundary risks.

2|Updated Feb 9, 2026
Search Tags:#automation#checklist#llm#sql#review#diff#pr
One-click install
npx skills add https://github.com/madebynoam/bryllen --skill review-madebynoam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/madebynoam/bryllen/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/madebynoam/bryllen --skill review-madebynoam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the pre-landing PR review by analyzing diffs against main to surface SQL safety concerns, LLM trust boundary violations, and other structural risks before merging.

Core Features & Use Cases

  • Two-pass PR review: critical checks for data safety and trust, followed by informational checks for conditional side effects, prompts, tests, and frontend consistency.
  • Actionable findings: file-level recommendations, remediation steps, and a structured PR description summary.
  • Integrations: guidance for triage and decision-making during code review.

Quick Start

Run the /review workflow on a pull request to begin the pre-landing analysis.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate a PR review to check SQL safety and LLM trust boundaries?▼

Automate PR review by analyzing code diffs against the main branch to detect SQL safety issues and LLM trust boundary violations. A two-pass scan applies a checklist to surface critical data risks first, then informational structural concerns.

What is the best way to generate a structured code review report from a diff?▼

Generate a code review report by analyzing diffs against a predefined checklist. The process produces file-level findings, recommended remediation steps, and a PR-descriptive summary to guide reviewers during the merge triage process.

Can I use an automated checklist to detect structural risks in a pull request before merging?▼

Use an automated checklist to detect structural risks in a pull request by evaluating conditional side effects, frontend consistency, and test coverage. The second pass of the review identifies these informational risks before generating an actionable summary.

Does PR diff analysis catch LLM trust boundary violations and data safety issues?▼

PR diff analysis catches LLM trust boundary violations and data safety issues during a critical first pass. It scans for these high-priority risks before moving to informational checks for prompts and structural formatting.

How do I review a code diff for conditional side effects and frontend consistency issues?▼

Review a code diff for conditional side effects and frontend consistency issues using an automated two-pass analysis. The informational second pass evaluates the diff against checklist rules to surface these specific structural risks.

When should I not rely on automated diff analysis for code review?▼

Do not rely on automated diff analysis when requiring deep business logic verification or complex architectural assessment. The automated review focuses strictly on predefined SQL safety, LLM trust boundaries, and structural diff risks.

Related Skills

Explore More Software Engineering Skills→
ather-techieather-techie
6

pr-description

Generate structured pull request descriptions from git diffs against the main branch.

Community
Basic
Jamie-CuiJamie-Cui
28

finishing-a-development-branch

Finalize feature branches with pre-integration checks and merge strategy guidance.

Community
Intermediate
nhattran998nhattran998

review

Analyze diffs against the base branch for SQL safety and trust boundary issues.

Community
Intermediate
antriksh-29antriksh-29

review

Analyzes diffs for SQL safety, LLM trust boundary violations, and side effects pre-merge.

Community
Advanced