security-review

Automate STRIDE-based security reviews of code changes and output JSON findings.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/lucking7/factory-plugins --skill security-review-lucking7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/lucking7/factory-plugins/tree/main/plugins/security-engineer/skills/security-review
Command: npx skills add https://github.com/lucking7/factory-plugins --skill security-review-lucking7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables rapid, comprehensive security reviews of code changes by applying STRIDE threat modeling, scanning for vulnerabilities, and validating findings for exploitability, ensuring secure patches can be produced efficiently.

Core Features & Use Cases

  • STRIDE-based threat modeling: identifies spoofing, tampering, repudiation, information disclosure, DoS, and elevation-of-privilege risks in code changes.
  • Commit/PR scan and validation: analyzes commits, PR diffs, and full repos, validating findings and producing structured outputs for patch generation.
  • Downstream integration: outputs findings in JSON formats (security-findings.json, validated-findings.json) for consumption by the security-patch-generation skill and CI workflows.

Quick Start

Trigger a security review on a PR by commenting: @droid security or run a full repository scan with @droid security --full. The skill auto-generates a threat model if missing and stores results for review.

Frequently Asked Questions about security-review

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

FAQPage Schema
How do I automate STRIDE threat modeling for pull request security reviews?

Automating STRIDE threat modeling for pull request security reviews is done by scanning PR diffs for spoofing, tampering, and elevation-of-privilege risks. The skill analyzes commits, validates findings for exploitability, and outputs standardized JSON files for patch generation.

Can I scan a full code repository for vulnerabilities without a pre-existing threat model?

You can scan a full code repository for vulnerabilities without a pre-existing threat model by running a full audit. The skill automatically generates a missing threat model, scans across multiple languages, and validates discovered exploitability risks for downstream patching.

How does STRIDE-based code review validate if a vulnerability is actually exploitable?

STRIDE-based code review validates if a vulnerability is actually exploitable by analyzing commits and PR diffs, then applying threat modeling categories like information disclosure and DoS. It confirms exploitability and outputs validated findings in structured JSON formats.

What is the best way to integrate security findings into automated patch generation workflows?

The best way to integrate security findings into automated patch generation workflows is by exporting standardized JSON files. The skill outputs security-findings.json and validated-findings.json, which are designed for direct consumption by the security-patch-generation skill and CI workflows.

Does the security review skill support scanning commits across different programming languages?

The security review skill supports scanning commits across different programming languages for vulnerabilities. It applies STRIDE-based threat modeling to code changes, validating findings for exploitability before delivering structured outputs for patch generation.