skills.rest
adityasingh2400
adityasingh2400COMMUNITY
Explore all skills by this author →
Website𝕏@NoeticPraxisGitHub

review

Analyze pull request diffs against the base branch for SQL safety and structural risks.

2|Updated Apr 4, 2026
Search Tags:#security#llm#review#diff#code-quality#pull-request#pr-review
One-click install
npx skills add https://github.com/adityasingh2400/SwarmSell --skill review-adityasingh2400
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/adityasingh2400/SwarmSell/tree/main/.claude/skills/review
Command: npx skills add https://github.com/adityasingh2400/SwarmSell --skill review-adityasingh2400

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR review analyzes diffs against the base branch to surface SQL safety risks, LLM trust boundary violations, conditional side effects, and other structural issues before merge.

Core Features & Use Cases

  • Pre-landing PR review: Analyzes diffs to identify potential risks and quality gaps before merging.
  • Proactively suggests changes to improve safety, clarity, and maintainability.
  • Useful for code reviews, PR audits, and diff checks across large changes.

Quick Start

Ask Claude to run a pre-landing PR review by diffing against the base branch and listing structural issues.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a pull request diff for SQL safety risks?▼

To review a pull request diff for SQL safety risks, analyze the changes against the base branch to surface injection vulnerabilities and structural issues before merging. This pre-landing review identifies database risks and proactively suggests code changes.

What is pre-landing code review and how does it identify LLM trust boundary violations?▼

Pre-landing code review analyzes pull request diffs to identify LLM trust boundary violations before code is merged. It checks if untrusted LLM outputs cross security boundaries without proper validation, surfacing these risks alongside conditional side effects.

How do I check a diff for conditional side effects before merging?▼

To check a diff for conditional side effects, run a pre-landing review that analyzes the pull request against its base branch. This process surfaces hidden state mutations and structural issues, providing actionable guidance to improve code quality.

Can I use automated PR audits for large code changes?▼

Yes, you can use automated PR audits for large code changes by analyzing the full diff against the base branch. This pre-landing review scales to surface structural issues, SQL risks, and LLM trust boundary violations across the entire changeset.

What is the best way to proactively suggest code changes during a PR review?▼

The best way to proactively suggest code changes during a PR review is to analyze the diff for structural issues and safety risks. This approach identifies gaps in safety, clarity, and maintainability, offering actionable guidance before merging.

Do I need a specific environment to check a diff for code quality and security risks?▼

No specific environment is required beyond the pull request diff itself. The review analyzes the diff against the base branch directly, requiring no additional dependencies to surface SQL risks, LLM boundary violations, and structural code quality issues.

Related Skills

Explore More Software Engineering Skills→
SeaLion-hubSeaLion-hub

review

Analyze pull request diffs for SQL safety, trust boundaries, and side effects.

Community
Advanced
JacobPEvansJacobPEvans
3

sync-main

Fetch remote main updates and merge them into the current branch.

Community
Intermediate
robertbr123robertbr123

requesting-code-review

Automate code review with security scans, quality checks, and automated fixes.

Community
Advanced
OneWave-AIOneWave-AI
245

code-review-pro

Review code for security vulnerabilities, performance bottlenecks, and maintainability issues.

Official
Basic