sc-diff-report

Scan changed files to classify and report security vulnerabilities during code reviews.

56|5|Updated Apr 8, 2026

Search Tags:#security #vulnerability #diff #scan #pr-review #changed-files

Ready to run

npx skills add https://github.com/ersinkoc/security-check --skill sc-diff-report

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sc-diff-report
Source: https://github.com/ersinkoc/security-check/tree/main/skills/sc-diff-report
Command: npx skills add https://github.com/ersinkoc/security-check --skill sc-diff-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly identify security issues in code changes by scanning only the files touched by a commit, PR, or diff, enabling faster and more focused reviews.

Core Features & Use Cases

Targeted analysis of changed files during PRs and commits to surface new and existing vulnerabilities.
Diff-aware reporting that classifies findings as new versus existing and includes context from nearby code.
Dependency-aware checks when relevant files are touched, enabling quick risk assessment during code review.

Quick Start

Run a diff-focused security scan on changed files to generate a security report.

Frequently Asked Questions about sc-diff-report

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

FAQPage Schema

How do I run a security scan on only the changed files in a pull request?▼

Run an incremental security scan on changed files to deliver focused results during PR reviews. Diff-aware discovery targets only the code touched by a commit or staged changes, classifying vulnerabilities as new or existing.

What is diff-aware vulnerability reporting and how does it work?▼

Diff-aware vulnerability reporting classifies security findings as new versus existing based on code changes. It analyzes touched files during commits or PRs and includes context from nearby code to speed up secure delivery reviews.

Can I check for dependency vulnerabilities when only relevant files are modified?▼

Yes, this approach performs dependency-aware checks when relevant files are touched. Targeting security scanning on changed files enables quick risk assessment during code review without scanning the entire repository.

What's the best way to speed up secure code delivery during commits?▼

The best way to speed up secure delivery is running targeted security scans on changed files. This diff-aware process works during PR reviews, commits, and staged changes to surface only relevant new and existing vulnerabilities.

Does incremental security scanning work with staged changes before a commit?▼

Yes, incremental security scanning works during PR reviews, commits, and staged changes. It implements diff-aware discovery on the files touched by these events to generate focused vulnerability reports.