security-review

Execute STRIDE-based security reviews with dependency vulnerability scanning and threat model analysis.

479|56|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/codexstar69/bug-hunter --skill security-review-codexstar69
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/codexstar69/bug-hunter/tree/main/skills/security-review
Command: npx skills add https://github.com/codexstar69/bug-hunter --skill security-review-codexstar69

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates in-depth security reviews for codebases, identifying vulnerabilities and potential threats using a structured, adversarial approach.

Core Features & Use Cases

  • STRIDE-based Security Audits: Performs focused reviews based on the STRIDE threat model.
  • Dependency Vulnerability Scanning: Integrates with dependency scanning to identify CVEs and assess reachability.
  • Threat Model Integration: Leverages existing threat models for context-aware analysis.
  • Use Case: Use this skill to conduct a comprehensive security audit of a new feature before it's merged, combining code analysis with dependency vulnerability checks.

Quick Start

Run a full repository security audit using the security-review skill.

Frequently Asked Questions about security-review

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

FAQPage Schema
How do I automate a STRIDE-based security audit for my codebase?

Automating a STRIDE-based security audit involves executing a structured threat model analysis to identify vulnerabilities across your repository. This skill integrates code analysis and dependency checks to perform comprehensive reviews before merges.

What is the best way to run a security review on a pull request?

The best way to run a security review on a pull request is using an automated validation process that scans code changes for vulnerabilities and checks dependency reachability for known CVEs.

Does automated security scanning check for dependency vulnerabilities and CVEs?

Yes, automated security scanning integrates dependency vulnerability scanning to identify known CVEs and assess their reachability within your codebase during the threat model analysis.

Do I need a threat-model.md file to perform a repository security scan?

Yes, you need native artifacts like a threat-model.md and dep-findings.json to perform a comprehensive repository security scan, as these files provide the necessary context for analysis.

Can I use threat model integration for weekly security scans?

Yes, you can leverage threat model integration for weekly security scans to maintain context-aware analysis and continuously identify potential vulnerabilities in your codebase.