differential-review

Analyze code changes for security vulnerabilities and regressions using git history.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/andrescardonas7/salchipapa-web --skill differential-review-andrescardonas7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: differential-review
Source: https://github.com/andrescardonas7/salchipapa-web/tree/main/.cursor/skills/differential-review
Command: npx skills add https://github.com/andrescardonas7/salchipapa-web --skill differential-review-andrescardonas7

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the security review of code changes (PRs, commits, diffs), identifying vulnerabilities, regressions, and assessing the blast radius of modifications.

Core Features & Use Cases

  • Security Vulnerability Detection: Analyzes code for common security flaws.
  • Regression Prevention: Uses git history to detect re-introduced vulnerabilities.
  • Blast Radius Calculation: Quantifies the potential impact of code changes.
  • Use Case: Before merging a pull request, use this Skill to perform a comprehensive security audit, ensuring no new vulnerabilities are introduced and existing ones are not re-introduced.

Quick Start

Use the differential review skill to analyze the security implications of the current git diff.

Frequently Asked Questions about differential-review

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

FAQPage Schema
How do I perform a security code review on a git diff before merging a pull request?

To perform a security code review on a git diff, you can automate the process to analyze pull requests for vulnerabilities, detect regressions using git history, calculate blast radius, and generate a comprehensive markdown report.

How does git history detect security regressions in code changes?

Git history detects security regressions by comparing new code changes against past commits, identifying if previously patched vulnerabilities are being re-introduced. This differential analysis helps prevent known flaws from re-entering the codebase.

Can I calculate the blast radius of code changes to assess potential impact?

Yes, you can calculate the blast radius of code changes to quantify the potential impact of modifications. This process assesses how far-reaching a change might be and identifies test coverage gaps to ensure stability.

Does the security review scale for large codebases with extensive diffs?

Yes, the security review scales for large codebases by adjusting the analysis depth based on repository size. It evaluates extensive diffs and commits while still providing comprehensive markdown reports on vulnerabilities and coverage gaps.

What is the best way to automate vulnerability detection in git commits?

The best way to automate vulnerability detection in git commits is using a differential review process that analyzes diffs for common security flaws, checks git history for regressions, and outputs a detailed markdown audit report.