review

Analyze code diffs and pull requests for safety and structural issues.

Updated May 4, 2026

Search Tags:#code quality #diff analysis #static analysis #code review #pull request #security

Ready to run

npx skills add https://github.com/VIethoangnguyenle/nexus-enterprise --skill review-viethoangnguyenle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/VIethoangnguyenle/nexus-enterprise/tree/main/.agent/skills/review
Command: npx skills add https://github.com/VIethoangnguyenle/nexus-enterprise --skill review-viethoangnguyenle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The review Skill helps developers and reviewers analyze code diffs and pull requests to identify structural issues, safety violations, and quality concerns, reducing manual review effort and errors.

Core Features & Use Cases

Diff Analysis: Compares code changes against base branches, highlighting potential safety violations and structural issues.
Code Review Guidance: Suggests improvements, detects security risks, and checks for best practices during pull request evaluations.
Use Case: When preparing to merge a feature, run this Skill to automatically flag SQL safety issues, trust boundary violations, and structural concerns, ensuring code quality before landing.

Quick Start

Ask the AI to review the pull request diff for security flaws and structural issues.

Frequently Asked Questions about review

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

FAQPage Schema

How do I analyze a pull request diff for security and structural issues?▼

To analyze a pull request diff, you can run a code review process that checks the changes against known bad patterns to detect safety violations, structural issues, and best practice violations before merging.

What is automated diff analysis used for in software engineering?▼

Automated diff analysis is used to compare code changes against base branches, highlighting potential safety risks like SQL issues and trust boundary violations to reduce manual review effort and errors.

How do I check code changes for SQL safety and trust boundary violations?▼

You can check code changes by analyzing the pull request diff for known bad patterns, which flags SQL safety issues, trust boundary violations, and structural concerns to ensure code quality before merging.

Does static analysis work for pre-landing code review sessions?▼

Yes, static analysis is designed for use during pre-landing or code review sessions to enhance quality assurance by detecting structural issues, safety violations, and best practice violations in the code diffs.

What is the best way to detect known bad patterns in code diffs?▼

The best way to detect known bad patterns in code diffs is to run an automated code review that analyzes the changes and checks for structural issues, safety violations, and best practice deviations.