secure-code-review

Audit codebases and diffs for security flaws and compliance risks.

3|2|Updated Jun 9, 2026

Search Tags:#security #vulnerability #owasp #risk-assessment #threat-modeling #static-analysis #code-review

Ready to run

npx skills add https://github.com/JayRHa/AgentSkills --skill secure-code-review-jayrha

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: secure-code-review
Source: https://github.com/JayRHa/AgentSkills/tree/main/secure-code-review
Command: npx skills add https://github.com/JayRHa/AgentSkills --skill secure-code-review-jayrha

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Review code through the eyes of an attacker to identify and prioritize security vulnerabilities, reducing risk before deployment.

Core Features & Use Cases

Map trust boundaries and taint data flows to dangerous sinks.
Rate findings by impact and exploitability using a standardized rubric.
Integrate with PR workflows to produce actionable fixes and mitigations.

Quick Start

Analyze the provided codebase or diff for security issues and generate prioritized findings.

Frequently Asked Questions about secure-code-review

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

FAQPage Schema

How do I audit code for security vulnerabilities in a pull request diff?▼

Threat modeling secures code by mapping trust boundaries and analyzing taint data flows to dangerous sinks. It identifies potential compliance risks and security flaws before deployment by reviewing the codebase through an attacker's perspective.

Can I apply static analysis for threat modeling across different programming languages?▼

Static analysis for threat modeling applies across different programming languages and build systems. It supports diverse codebases by generating structured reports and actionable mitigations based on standardized security checklists.

What is the best way to rate security findings by impact and exploitability?▼

The best way to rate security findings by impact and exploitability is using a standardized rubric. This approach evaluates discovered vulnerabilities and compliance risks to produce actionable fixes and structured mitigation reports.

How do I map trust boundaries and taint data flows during a security review?▼

Mapping trust boundaries and taint data flows during a security review involves tracing untrusted input to dangerous execution sinks. This exposes potential security vulnerabilities, enabling structured reporting and prioritized remediation.

Does secure code review work with OWASP risk assessment methodologies?▼

Secure code review aligns with OWASP risk assessment methodologies by mapping threats and tracking taint flows to dangerous sinks. It rates identified vulnerabilities by impact and exploitability to generate actionable fixes for pull requests.