tob-diff-review

Performs security-focused differential review of code changes from PRs, commits, or diffs.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Ayoub-ouederni/SENTINEL --skill tob-diff-review-ayoub-ouederni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tob-diff-review
Source: https://github.com/Ayoub-ouederni/SENTINEL/tree/main/.claude/skills/tob-diff-review
Command: npx skills add https://github.com/Ayoub-ouederni/SENTINEL --skill tob-diff-review-ayoub-ouederni

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing code changes for security issues is time-consuming and easy to get wrong when done manually, especially across large pull requests or commit ranges. This Skill automates a security-focused differential review so vulnerabilities introduced by changes are surfaced systematically. ## Core Features & Use Cases - Flexible Target Input: Accepts a PR URL, commit SHA, or local diff path as the review target. - Optional Baseline Comparison: Supports a --baseline <ref> argument to compare changes against a specific reference point. - Delegated Workflow: Invokes the differential-review skill to execute the full security review workflow. - Use Case: Before merging a pull request into a smart contract repository, run a differential security review on the PR to identify newly introduced vulnerabilities compared to the main branch. ## Quick Start Run a differential security review on pull request number 42 of the current repository with main as the baseline.

Frequently Asked Questions about tob-diff-review

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

FAQPage Schema
How do I run a security review on a pull request?

Provide the PR URL as the target argument to the differential review. The skill parses the pull request changes and runs a security-focused review of the modified code against the repository context.

How to compare code changes against a specific baseline branch?

Pass the --baseline flag followed by a git reference such as a branch name or commit SHA. The review then evaluates the changes relative to that reference instead of the default comparison point.

What input formats does differential code review accept?

The review accepts three target types: a pull request URL, a commit SHA, or a path to a local diff file. Exactly one target is required for each review run.

Can I review a single commit for security issues?

Yes, pass the commit SHA as the target argument. The skill analyzes the changes introduced by that commit and flags potential security concerns in the modified code.

What are the limitations of automated differential security review?

Automated review focuses on the changed code and may miss vulnerabilities spanning unchanged context or requiring runtime behavior analysis. Findings should be validated manually before being treated as confirmed vulnerabilities.