security-review

Audit codebases for OWASP Top 10 vulnerabilities and hardcoded secrets.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/suhwan/claude-registry --skill security-review-suhwan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/suhwan/claude-registry/tree/main/skills/quality/security-review
Command: npx skills add https://github.com/suhwan/claude-registry --skill security-review-suhwan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code security reviews are time-consuming and error-prone when done manually. This Skill automates a thorough security assessment to uncover OWASP Top 10 vulnerabilities, hardcoded secrets, and insecure patterns in codebases, enabling faster, safer deployments.

Core Features & Use Cases

  • OWASP Top 10 Scan: Detects common vulnerabilities and provides remediation guidance.
  • Secrets Detection: Finds hardcoded API keys, passwords, and tokens to prevent credential leakage.
  • Input Validation & Authentication Review: Evaluates input sanitization, authorization checks, and session security.
  • Dependency Security: Scans dependencies for known CVEs and outdated components.
  • Use Case: Pre-deploy security checks, security sprint audits, or ongoing codebase assessments across languages.

Quick Start

Run a full security review on your repository to generate a detailed security report and actionable fixes.

Frequently Asked Questions about security-review

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

FAQPage Schema
How do I automate an OWASP Top 10 vulnerability scan for my codebase?

To automate an OWASP Top 10 vulnerability scan, this Skill evaluates your codebase to detect common security flaws and generates a markdown report containing identified issues, severities, and remediation guidance.

What is the best way to detect hardcoded secrets and API keys before deployment?

Detecting hardcoded secrets and API keys before deployment is handled by scanning your repository for credentials to prevent leakage, outputting a detailed security report with locations and remediation steps.

How does dependency security scanning work for known CVEs?

Dependency security scanning works by evaluating your project's dependencies against known CVEs and outdated components, producing a markdown report that flags vulnerable libraries and provides actionable fixes.

Can I perform a security audit across multiple programming languages and environments?

You can perform a security audit across multiple languages and environments, as the Skill evaluates repositories undergoing development, review, or pre-deployment security sprints for input validation and authentication controls.

Does the security review check input validation and authentication controls?

The security review does check input validation and authentication controls by evaluating input sanitization, authorization checks, and session security, then documenting any identified vulnerabilities in a markdown report.

What is included in the markdown security report generated by the codebase audit?

The markdown security report includes identified security issues, their severities, exact locations in the code, relevant CVEs for dependencies, and specific remediation guidance to resolve the vulnerabilities.