review

Analyze code diffs against main for structural and security issues.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/yamparalarahul27/illu-ic --skill review-yamparalarahul27
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/yamparalarahul27/illu-ic/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/yamparalarahul27/illu-ic --skill review-yamparalarahul27

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of reviewing code changes in a Pull Request (PR) before they are merged, catching structural issues, potential bugs, and security vulnerabilities that automated tests might miss.

Core Features & Use Cases

  • Automated Code Analysis: Scans code diffs against the main branch for critical issues like SQL injection risks, LLM trust boundary violations, and race conditions.
  • Checklist-Driven Review: Follows a predefined checklist to ensure comprehensive checks across various categories.
  • Greptile Integration: Incorporates feedback from the Greptile bot for a more thorough review.
  • Use Case: A developer submits a PR. Before merging, they run this Skill to get an immediate, detailed analysis of potential problems, ensuring code quality and security.

Quick Start

Run the review skill to analyze the current branch's diff against main.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate pull request code review before merging?

Automated pull request code review analyzes branch diffs against main to detect critical structural issues, SQL injection risks, and LLM trust boundary violations before merging. It follows a checklist-driven approach to catch bugs and security vulnerabilities that automated tests often miss.

What security vulnerabilities can pre-landing code review catch in a diff?

Pre-landing code review catches security vulnerabilities in a diff such as SQL injection risks, LLM trust boundary violations, and race conditions. It scans code changes against the main branch to identify these critical problems before they are merged.

How do I check code diffs for LLM trust boundary violations?

Checking code diffs for LLM trust boundary violations involves analyzing pull request changes against the main branch for unsafe trust boundaries. This automated review process identifies potential security issues where LLM inputs might bypass safety constraints.

Does this automated code review work with Greptile integration?

Yes, this automated code review incorporates Greptile integration to provide enhanced and thorough analysis. It combines checklist-driven feedback with Greptile bot insights to deliver actionable fixes for structural issues and potential bugs.

Can I use automated PR review for SQL safety and race condition detection?

Yes, you can use automated PR review for SQL safety and race condition detection. It scans code diffs against the main branch specifically targeting these critical issues alongside conditional side effects and LLM trust boundary violations.

What are the limitations of automated code analysis for pull requests?

Automated code analysis for pull requests focuses on structural issues, SQL safety, and LLM trust boundaries but may miss complex business logic errors. It supplements but does not replace human review or automated testing workflows.