commit-security-scan

You can scan code changes for security vulnerabilities by applying threat-model patterns to analyze PR diffs. This process surfaces STRIDE-based findings with actionable remediation steps directly within your code review workflow.

STRIDE-based threat modeling for code diffs is an AI-powered analysis method that identifies security vulnerabilities in code changes. It applies structured threat categories to surface potential risks during pre-commit checks or branch comparisons.

Yes, security scanning requires a threat model at .factory/threat-model.md and a security config at .factory/security-config.json to load context and severity thresholds. The skill can auto-generate these prerequisite files if they are missing.

Yes, AI security scanning applies to pre-commit checks, PR reviews, and branch comparisons across any repository. It analyzes your code diffs using LLM reasoning to identify vulnerabilities before changes are merged.

Automating vulnerability detection in CI-CD pipelines is best achieved by applying threat-model-driven analysis to your code diffs. This method surfaces STRIDE-based findings during automated code reviews without requiring manual security audits.

AI-powered security analysis relies on LLM reasoning and a predefined threat model to identify vulnerabilities. It requires a properly configured .factory/threat-model.md file to establish context and severity thresholds for accurate STRIDE-based findings.