security-review

Automate vulnerability scanning during PR reviews by invoking this Skill to apply STRIDE threat modeling, validate findings, and generate structured patches for downstream remediation.

STRIDE threat modeling for code changes is a structured method to identify and validate security vulnerabilities by categorizing threats like spoofing, tampering, and information disclosure across repository audits.

Yes, you need a threat model file at .factory/threat-model.md to guide the security audit, or you can have the Skill generate this artifact to proceed with structured remediation.

Yes, you can run a full repository security audit without manual code review by executing this Skill to generate a STRIDE threat model and output a validated findings report automatically.

The best way to generate patches for security vulnerabilities is using a structured STRIDE analysis that produces validated findings, enabling downstream skills to apply targeted code remediation.

Yes, weekly vulnerability scanning requires a threat model artifact at .factory/threat-model.md to structure the STRIDE analysis and validate security findings for ongoing code reviews.