Differential Security Review

Analyze git diffs to categorize security risks and generate a differential security report.

1|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/BasharAmso/Bashi --skill differential-security-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Differential Security Review
Source: https://github.com/BasharAmso/Bashi/tree/main/create-bashi-app/template/custom-skills/differential-security-review
Command: npx skills add https://github.com/BasharAmso/Bashi --skill differential-security-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review code changes through a security lens to identify potential vulnerabilities introduced by diffs and to ensure compliance with security practices.

Core Features & Use Cases

  • Analyze git diff to categorize risk across modified files.
  • Produce a differential security report and update relevant state tracking.
  • Useful for pre-merge reviews, security sprints, and audit trails.

Quick Start

Review the latest diff (staged, unstaged, or branch comparison) and generate a differential security report with an updated STATE.md.

Frequently Asked Questions about Differential Security Review

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

FAQPage Schema
How do I automate a security audit for a git diff?

To automate a security audit for a git diff, you need a tool that analyzes code changes and categorizes findings by risk. This process reviews branch diffs, staged changes, or pull requests to surface potential vulnerabilities during code reviews.

What is differential security review and when do I need it?

Differential security review identifies the security implications of code changes reflected in diffs. You need it during pre-merge reviews, security sprints, and audit trails to ensure new code complies with security practices before integration.

How do I generate a security report for staged and unstaged changes?

Generating a security report for staged and unstaged changes involves analyzing the git diff to categorize risk across modified files. This workflow produces a differential security report and updates the project state tracking file.

Can I assess the security risk of a pull request before merging?

Yes, you can assess the security risk of a pull request before merging by applying a structured workflow to the branch comparison. This surfaces potential vulnerabilities introduced by the diff and ensures compliance with security practices.

Does this security review process require any external dependencies?

No, this security review process does not require external dependencies. It directly analyzes your git diffs to categorize risk across modified files and generates a differential security report without needing additional components.