skills.rest
ClyptAI
ClyptAIOFFICIAL
Explore all skills by this author →
GitHub

review

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

Updated Mar 8, 2026
Search Tags:#security#llm#review#diff#lint#pull-request
One-click install
npx skills add https://github.com/ClyptAI/Clypt-Backend --skill review-clyptai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/ClyptAI/Clypt-Backend/tree/main/.agents/skills/gstack/review
Command: npx skills add https://github.com/ClyptAI/Clypt-Backend --skill review-clyptai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diff-heavy code review can miss critical architectural or security issues. The Review skill analyzes diffs against the base branch to surface SQL safety concerns, LLM trust boundary violations, and conditional side effects, ensuring PRs land with fewer surprises.

Core Features & Use Cases

  • Automated diff-analysis: highlights potential SQL risks, LLM prompt leakage, and unsafe changes in a PR.
  • Structural integrity checks: identifies routing gaps, side-effect risks, and maintainability concerns before merge.
  • Proactive guidance: suggests concrete next steps for reviewers and authors during pre-landing checks.

Quick Start

Provide the PR diff or link and ask me to run a pre-landing review

Frequently Asked Questions about review

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

FAQPage Schema
How do I run an automated pre-landing review on a pull request diff?▼

To run an automated pre-landing review, provide the PR diff or link and request a review. The skill analyzes the diff against the base branch to surface SQL safety issues, LLM trust boundary violations, and structural concerns before merging.

What is automated diff analysis for pull requests?▼

Automated diff analysis for pull requests is the process of evaluating code changes against a base branch to identify SQL risks, LLM prompt leakage, and unsafe structural modifications. This ensures PRs land with fewer unexpected architectural or security surprises.

Can I identify LLM trust boundary violations in my code before merge?▼

Yes, you can identify LLM trust boundary violations before merge by analyzing your PR diff. The review process specifically highlights potential prompt leakage and unsafe changes to ensure LLM integrations remain secure prior to landing.

What is the best way to catch SQL safety issues in a code review?▼

The best way to catch SQL safety issues in a code review is using an automated diff analysis workflow. It evaluates pull request changes against the base branch to proactively surface SQL risks and provide actionable feedback before merging.

What structural integrity checks does a pre-merge diff analysis include?▼

Pre-merge diff analysis structural integrity checks include identifying routing gaps, conditional side-effect risks, and maintainability concerns. It applies a standardized review workflow to ensure consistent validation and proactive guidance for authors and reviewers.

Does pre-landing PR review work without adding external dependencies?▼

Yes, pre-landing PR review works without adding external dependencies. The skill operates natively by applying a standardized review workflow to analyze provided diffs, ensuring consistent validation and actionable feedback across any repository.

Related Skills

Explore More Software Engineering Skills→
bhianerdbhianerd
1

review

Review pull request diffs for SQL safety, LLM trust boundaries, and concurrency hazards.

Community
Advanced
geoffreywoogeoffreywoo

review

Analyze PR diffs for SQL safety, trust boundary violations, and side effects.

Community
Advanced
yanochka11yanochka11

review

Analyze repository diffs to identify defects, security risks, and structural problems.

Community
Advanced
ligianehualigianehua

review

Analyze git diffs for SQL safety, LLM trust boundaries, and structural defects.

Community
Advanced