commit-security-scan

Automate security analysis of code changes with threat-model patterns.

101|10|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/Factory-AI/factory-plugins --skill commit-security-scan-factory-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-security-scan
Source: https://github.com/Factory-AI/factory-plugins/tree/main/plugins/security-engineer/skills/commit-security-scan
Command: npx skills add https://github.com/Factory-AI/factory-plugins --skill commit-security-scan-factory-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze code changes (PRs, commits, and diffs) to detect security vulnerabilities using LLM reasoning and threat-model patterns, accelerating secure code reviews.

Core Features & Use Cases

  • Automates security analysis of code changes during PR reviews, pre-commit checks, and branch comparisons.
  • Applies threat-model-based pattern matching to identify STRIDE categories across diffs and commits.
  • Generates actionable findings and guidance for remediation, integrated into review workflows.

Quick Start

Provide a code change request and I will automatically generate a threat model and security config if missing, then analyze the changes and produce a findings report.

Frequently Asked Questions about commit-security-scan

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

FAQPage Schema
How do I automate security reviews for code changes in pull requests?▼

To automate security reviews for code changes, you provide a pull request, commit, or diff. The tool analyzes the changed files using threat-model patterns to detect vulnerabilities and generates a findings report with remediation guidance.

What is threat-model based pattern matching for vulnerability detection?▼

Threat-model based pattern matching for vulnerability detection applies STRIDE categories to code diffs to identify security risks. It uses LLM-powered reasoning to evaluate changes and produce actionable findings for remediation.

Do I need a pre-existing threat model to analyze PRs for security issues?▼

You do not need a pre-existing threat model to analyze PRs for security issues. If a threat model and security configuration are missing, the tool auto-generates them and guides mitigations for your code changes.

How do I run pre-commit checks to detect vulnerabilities in my code diff?▼

To run pre-commit checks for vulnerability detection, provide your code diff to the analyzer. It evaluates the changed files against threat-model patterns and outputs actionable findings to secure your code before commit.

Can I use this for branch comparisons to find security issues?▼

You can use this for branch comparisons to find security issues by analyzing the diffs between branches. It applies LLM reasoning and STRIDE threat-model categories to the changed files to identify vulnerabilities.