skills.rest
smarmen86
smarmen86COMMUNITY
Explore all skills by this author →
GitHub

review

Analyze git diffs against base branches for SQL vulnerabilities and code defects.

Updated Jun 5, 2026
Search Tags:#automation#git#code review#pull request#security#diff
One-click install
npx skills add https://github.com/smarmen86/claude-code-kit --skill review-smarmen86
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/smarmen86/claude-code-kit/tree/main/skills/review
Command: npx skills add https://github.com/smarmen86/claude-code-kit --skill review-smarmen86

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the risk of introducing bugs, security vulnerabilities, or structural issues during the code review process by providing an automated, context-aware analysis of your diffs.

Core Features & Use Cases

  • Automated Diff Analysis: Scans code changes against the base branch to identify SQL safety issues, trust boundary violations, and conditional side effects.
  • Proactive Guidance: Offers pre-landing reviews to catch structural problems before they are merged into the codebase.
  • Use Case: When you are ready to merge a complex feature branch, invoke this skill to perform a comprehensive check of your diff, ensuring that your changes adhere to project standards and do not introduce regressions.

Quick Start

Invoke the review skill to perform a pre-landing analysis of the current pull request diff.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate git diff analysis to detect SQL vulnerabilities before merging a pull request?▼

Automated git diff analysis detects SQL vulnerabilities by scanning code changes against a base branch, identifying trust boundary violations and structural defects to ensure safer pre-merge validation. It proactively catches security boundary issues before integration.

What is automated code review for pull requests and how does it handle trust boundaries?▼

Automated code review for pull requests evaluates git diffs against the base branch to enforce proactive security boundary checks. It identifies trust boundary violations and conditional side effects, preventing structural regressions from merging into the codebase.

Can I use automated diff analysis to check for structural code defects in my feature branch?▼

Yes, you can use automated diff analysis to check feature branches for structural code defects. By comparing changes against the base branch, the analysis identifies conditional side effects and structural regressions before pre-landing code merges.

When do I need to run an automated pre-landing review on my git diff?▼

You need to run an automated pre-landing review when preparing complex pull requests for merge. This validates that your git diff adheres to project standards and proactively catches structural problems and security vulnerabilities before code integration.

Does automated pull request analysis work without external dependencies?▼

Automated pull request analysis works without external dependencies, relying solely on the git diff between your feature and base branches. It independently evaluates code changes to detect SQL safety issues and structural defects during pre-merge validation.

Related Skills

Explore More Software Engineering Skills→
yocxy2yocxy2

review

Analyze git diffs for SQL safety, concurrency, and LLM trust boundary violations.

Community
Advanced
ajsai47ajsai47
11

review

Analyze git diffs for SQL injection, race conditions, and shell injection risks.

Community
Advanced
howdeployhowdeploy
15

review

Analyze pull request diffs for SQL safety and trust boundary issues.

Community
Advanced
Serg28Serg28

security-reviewer

Automate security audits with semgrep, trivy, gitleaks, and dependency scanners.

Community
Intermediate