review-code-security

Review code changes for security vulnerabilities in authentication, input validation, and dependencies.

32|7|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/OzeroHAX/AssistAgents --skill review-code-security
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-code-security
Source: https://github.com/OzeroHAX/AssistAgents/tree/main/templates/skills/review/code/security
Command: npx skills add https://github.com/OzeroHAX/AssistAgents --skill review-code-security

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies and mitigates security vulnerabilities in code changes, ensuring that sensitive data, access controls, and dependencies are handled securely before deployment.

Core Features & Use Cases

  • AuthN/AuthZ Enforcement: Verifies that permissions are strictly enforced on the server-side.
  • Input Validation: Checks that all untrusted data is properly validated and normalized to prevent injection attacks.
  • Data Exposure Prevention: Ensures no secrets or Personally Identifiable Information (PII) are leaked in responses, logs, or error messages.
  • Dependency Hygiene: Assesses the risk associated with new dependencies.
  • Use Case: Before merging a pull request that modifies user authentication logic or handles payment information, this Skill performs a critical security review to prevent potential breaches.

Quick Start

Run a security review on the latest code changes to check for authentication bypasses and data exposure risks.

Frequently Asked Questions about review-code-security

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

FAQPage Schema
How do I perform a security code review on a pull request?

You can prevent data exposure by checking responses, logs, and error messages for leaked secrets or PII. The review ensures no sensitive data is exposed during code changes.

Can I check new dependencies for security risks before merging?

Yes, the review enforces AuthN/AuthZ by verifying that permissions are strictly enforced on the server-side. This prevents unauthorized access and ensures access controls are securely handled.

How does input validation prevent injection attacks in code reviews?

Input validation prevents injection attacks by checking that all untrusted data is properly validated and normalized. This ensures external inputs are sanitized before processing.

Do I need to provide access model details for a security vulnerability check?

Yes, providing access model details is required for a security vulnerability check. The review needs this context to accurately identify authentication bypasses and enforce server-side permissions.