review-security

Audit changed code for security vulnerabilities without applying fixes.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/0xdeafcafe/skills --skill review-security-0xdeafcafe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-security
Source: https://github.com/0xdeafcafe/skills/tree/main/skills/review-security
Command: npx skills add https://github.com/0xdeafcafe/skills --skill review-security-0xdeafcafe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill performs a focused, read-only security audit on the files changed in a PR or working tree so you can catch vulnerabilities, secret leaks, missing authorization checks, and unsafe dependencies before code is merged.

Core Features & Use Cases

  • Diff-based security review: Audits touched files for authn/authz gaps, input validation issues, output encoding mistakes, CSRF, SSRF, CORS, session, crypto, and deserialization risks.
  • Dependency and secret scanning: Runs ecosystem-specific vulnerability tools where available and checks for hardcoded credentials or exposed tokens.
  • Structured findings output: Emits prioritized findings in a consistent finding schema with severity levels and fix guidance, including decide-required cases for sensitive issues like live secret exposure.
  • Use Case: When a PR adds a new route, updates package dependencies, and changes auth-related code, use this Skill to get a security-only verdict without modifying any files.

Quick Start

Ask the assistant to run review-security on the current PR or working tree and return only security findings.

Frequently Asked Questions about review-security

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

FAQPage Schema
How do I audit a pull request for security vulnerabilities?

To audit a pull request for security vulnerabilities, run a read-only security review on the changed files. This process checks for authorization gaps, input validation issues, and unsafe dependencies without applying any fixes to the working tree.

What does diff-based code review check for in a new route?

Diff-based code review checks new routes for authentication, authorization, input validation, output encoding, CSRF, SSRF, CORS, session, crypto, and deserialization risks. It analyzes only the touched files to identify potential security exposures before merging.

Can I scan for hardcoded secrets and vulnerable dependencies in Python and npm projects?

Yes, you can scan for hardcoded secrets and vulnerable dependencies in Python and npm projects. The review process runs ecosystem-specific audit tools across npm, Python, Rust, and Go to detect exposed tokens and unsafe package dependencies.

Does security code review automatically fix vulnerable code?

Security code review does not automatically fix vulnerable code. It performs a read-only analysis and emits findings in a structured severity-based schema with explicit fix guidance, requiring manual intervention to resolve the identified vulnerabilities.

How are security findings reported after a dependency audit and secret scan?

Security findings are reported in a consistent structured schema with severity levels and fix guidance after a dependency audit and secret scan. The output includes prioritized vulnerabilities and explicit coverage-gap reporting for sensitive issues like live secret exposure.