commit-security-scan

Scan code changes for security vulnerabilities using STRIDE context.

479|56|Updated Mar 7, 2026

Search Tags:#code review #security #vulnerability #STRIDE #threat model #commit scan

Ready to run

npx skills add https://github.com/codexstar69/bug-hunter --skill commit-security-scan-codexstar69

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-security-scan
Source: https://github.com/codexstar69/bug-hunter/tree/main/skills/commit-security-scan
Command: npx skills add https://github.com/codexstar69/bug-hunter --skill commit-security-scan-codexstar69

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the critical need to identify security vulnerabilities within code changes before they are merged, reducing the risk of introducing exploitable weaknesses into a codebase.

Core Features & Use Cases

Targeted Security Scanning: Focuses specifically on security issues in changed code, making it ideal for rapid reviews.
STRIDE Threat Modeling: Analyzes code against the STRIDE framework (Spoofing, Tampering, Repudiation, Information Disclosure, DoS, Elevation of Privilege).
Use Case: When preparing a pull request, use this Skill to perform a quick security check on your modifications to ensure no new vulnerabilities are introduced.

Quick Start

Use the commit-security-scan skill to review the security of my staged code changes.

Frequently Asked Questions about commit-security-scan

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

FAQPage Schema

How do I scan code changes for security vulnerabilities before merging?▼

Scanning code changes for security vulnerabilities targets staged code, pull requests, or commit diffs to identify exploitable weaknesses pre-merge. This process focuses on modified files and resolves the changed scope to detect security issues.

What is STRIDE threat model based code review?▼

STRIDE threat model based code review analyzes modifications against Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege categories. This framework contextualizes identified issues within specific threat vectors.

Do I need threat model context to perform a commit security scan?▼

Yes, a commit security scan requires threat-model context to resolve changed-file scope for STRIDE-oriented issue detection. Providing this context ensures the security review accurately targets relevant vulnerabilities in your modifications.

Can I use this security scan for staged changes and branch comparisons?▼

Yes, this security scan applies to staged-change security checks, branch-comparison security review, and pre-merge security analysis of changed code. It targets security issues specifically within the modified files of those code changes.

What is the best way to review pull request diffs for security flaws?▼

Reviewing pull request diffs for security flaws is best accomplished by applying the STRIDE framework to the changed code scope. This targeted security scanning focuses exclusively on modifications to identify newly introduced vulnerabilities.