pelizzai-oswap

Analyze code diffs against the OWASP Top 10:2025 framework for vulnerabilities.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/rpelizza/PelizzAI --skill pelizzai-oswap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pelizzai-oswap
Source: https://github.com/rpelizza/PelizzAI/tree/main/.agents/skills/pelizzai-oswap
Command: npx skills add https://github.com/rpelizza/PelizzAI --skill pelizzai-oswap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the risk of introducing security vulnerabilities during development by providing a structured, automated review of code changes against the OWASP Top 10:2025 framework.

Core Features & Use Cases

  • Security Surface Analysis: Automatically identifies trust boundaries and security-sensitive code paths in your diffs.
  • Evidence-Based Review: Enforces a rigorous finding-and-proof methodology, requiring developers to provide a path of exploitation or safe failure for every identified risk.
  • Use Case: When modifying authentication logic or handling external user input, this skill ensures that potential injection, access control, or cryptographic failures are documented and mitigated before the code is integrated.

Quick Start

Use the pelizzai-oswap skill to perform a security review on the current pending changes in the repository.

Frequently Asked Questions about pelizzai-oswap

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

FAQPage Schema
How do I perform an automated OWASP security review on code changes?

Automated OWASP security review of code changes is performed by evaluating pending diffs against the OWASP Top 10:2025 framework, analyzing trust boundaries and security-sensitive paths to detect exploitation risks before integration.

What is the OWASP Top 10:2025 framework analysis for code diffs?

OWASP Top 10:2025 framework analysis for code diffs is an automated security analysis process that identifies vulnerabilities in authentication, authorization, and data handling by mapping potential exploitation paths within security-sensitive code modifications.

Can I use this to analyze pull requests for authorization and authentication vulnerabilities?

Yes, you can analyze pull requests for authorization and authentication vulnerabilities by evaluating pending changes to detect potential exploitation paths and ensure secure integration using systematic evidence synthesis.

How does the security review validate potential vulnerabilities in the code?

The security review validates potential vulnerabilities by enforcing a rigorous finding-and-proof methodology, requiring developers to map an exploitation path or demonstrate safe failure for every identified risk.

When do I need to perform an automated security analysis on file ranges?

You need to perform automated security analysis on file ranges when modifying authentication logic or handling external user input, ensuring injection, access control, or cryptographic failures are mitigated before code integration.