reviewing-security

Audit code changes for OWASP Top 10 vulnerabilities and severity.

8|1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/bostonaholic/team --skill reviewing-security-bostonaholic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-security
Source: https://github.com/bostonaholic/team/tree/main/skills/reviewing-security
Command: npx skills add https://github.com/bostonaholic/team --skill reviewing-security-bostonaholic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the risk of introducing vulnerabilities during development by providing a structured, repeatable methodology for security reviews.

Core Features & Use Cases

  • Attack Surface Analysis: Systematically identifies code areas exposed to user input, authentication, and external services.
  • OWASP Compliance: Guides the user through critical checks including Injection, XSS, and Broken Authentication.
  • Severity Classification: Provides a clear framework for categorizing findings from CRITICAL to LOW to ensure appropriate prioritization.
  • Use Case: Use this skill when performing a pull request review to ensure that new features do not introduce common security flaws like hardcoded secrets or insecure deserialization.

Quick Start

Invoke the reviewing-security skill to audit the current git diff for potential vulnerabilities and security risks.

Frequently Asked Questions about reviewing-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 git diff?

You can perform a security code review by systematically identifying attack surfaces in the git diff and applying OWASP Top 10 vulnerability checks to detect injection, authentication flaws, and sensitive data exposure.

What is OWASP compliance checking in code changes?

OWASP compliance checking in code changes involves evaluating updates against critical security risks like Injection, XSS, and Broken Authentication to prevent introducing common vulnerabilities during development.

How do I classify the severity of security vulnerabilities found during a code audit?

Classify security vulnerability severity using a standardized ladder ranging from CRITICAL to LOW, ensuring appropriate prioritization of remediation efforts for identified findings during the code audit.

Can I audit a pull request for hardcoded secrets and insecure deserialization?

Yes, you can audit a pull request for hardcoded secrets and insecure deserialization by analyzing attack surfaces and applying structured security checks to ensure new features do not introduce flaws.

What is attack surface analysis in software security audits?

Attack surface analysis in software security audits systematically identifies code areas exposed to user input, authentication mechanisms, and external services to evaluate potential vulnerability entry points.