security-review

Audit code for OWASP Top 10 vulnerabilities, hardcoded secrets, and unsafe patterns.

6|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Weihong-Liu/GenericAgent_project --skill security-review-weihong-liu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/Weihong-Liu/GenericAgent_project/tree/main/.codex/skills/security-review
Command: npx skills add https://github.com/Weihong-Liu/GenericAgent_project --skill security-review-weihong-liu

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of conducting a thorough security audit on code, identifying vulnerabilities and ensuring code integrity before deployment.

Core Features & Use Cases

  • Security Audit: Runs a comprehensive security review checking for OWASP Top 10 vulnerabilities, hardcoded secrets, and unsafe patterns.
  • Use Cases: After writing code that handles user input, after adding new API endpoints, before deploying to production, and after adding external dependencies.
  • Integration: Can be integrated with other skills for team-based security reviews, swarm-based parallel reviews, and Ralph-based continuous security review cycles.

Quick Start

Run a security review on the codebase by executing the 'security-review' command.

Frequently Asked Questions about security-review

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

FAQPage Schema
How do I run a security audit to check code for OWASP Top 10 vulnerabilities?

To run a security audit, execute the 'security-review' command on your codebase. This triggers a comprehensive check identifying OWASP Top 10 vulnerabilities, hardcoded secrets, and unsafe patterns before deployment.

When should I perform a code security review before deployment?

Perform a code security review after writing code that handles user input, adding new API endpoints, or integrating external dependencies. It ensures code integrity by identifying unsafe patterns and hardcoded secrets before production deployment.

How do I scan my codebase for hardcoded secrets and unsafe patterns?

Scanning for hardcoded secrets and unsafe patterns requires executing the 'security-review' command. The audit requires codebase access and utilizes external tools specifically for vulnerability scanning and secrets detection.

Can I integrate automated vulnerability scanning into team-based code reviews?

Yes, automated vulnerability scanning supports integration with other skills for team-based security reviews, swarm-based parallel reviews, and Ralph-based continuous security review cycles to ensure comprehensive code integrity.

What external tools do I need for dependency scanning and secrets detection?

Dependency scanning and secrets detection require access to external tools for vulnerability scanning. The security audit integrates these external tools alongside your codebase access to identify unsafe patterns and hardcoded secrets.