owasp-review

Identify OWASP Top 10 security vulnerabilities in code diffs.

746|130|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/Archive228/loopkit --skill owasp-review-archive228
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: owasp-review
Source: https://github.com/Archive228/loopkit/tree/main/skills/owasp-review
Command: npx skills add https://github.com/Archive228/loopkit --skill owasp-review-archive228

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill identifies security vulnerabilities in code changes against the OWASP Top 10, ensuring code quality and security before merging.

Core Features & Use Cases

  • Security Review: Checks for OWASP Top 10 vulnerabilities in code diffs.
  • Use Case: Before merging any code change, use this skill to scan for SQL injection, broken access control, authentication flaws, and other OWASP Top 10 issues.

Quick Start

Run the owasp-review skill on your code diff to identify potential security issues.

Frequently Asked Questions about owasp-review

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

FAQPage Schema
How do I scan a code diff for OWASP Top 10 vulnerabilities before merging?

Scanning a code diff for OWASP Top 10 vulnerabilities involves analyzing the changes against security standards to catch issues like SQL injection and broken access control before merging.

What is OWASP Top 10 code review and when do I need it?

OWASP Top 10 code review is the process of identifying security vulnerabilities in code changes based on OWASP standards. You need it during pre-merge reviews to ensure common web application security issues are resolved.

Can I use this security review to detect broken access control in code changes?

Yes, you can use this security review to detect broken access control in code changes. It analyzes diffs against OWASP Top 10 criteria to identify authentication flaws, access control issues, and other common web vulnerabilities.

What's the best way to automate vulnerability scanning for pre-merge code reviews?

The best way to automate vulnerability scanning for pre-merge code reviews is to run an OWASP-focused diff analysis on the code changes. This directly compares modifications against OWASP Top 10 criteria to pinpoint security flaws.

Does this vulnerability scanning check the entire codebase or just the code diff?

This vulnerability scanning checks just the code diff rather than the entire codebase. It focuses on analyzing code changes against OWASP Top 10 standards specifically for pre-merge code reviews.