security-analyst

Analyze code for OWASP Top 10 and Laravel-specific security vulnerabilities with severity ratings.

Updated Feb 11, 2026

Search Tags:#code review #security #vulnerability #owasp #analysis #laravel

Ready to run

npx skills add https://github.com/juniorfontenele/ai-guidelines --skill security-analyst-juniorfontenele

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-analyst
Source: https://github.com/juniorfontenele/ai-guidelines/tree/main/.agents/skills/security-analyst
Command: npx skills add https://github.com/juniorfontenele/ai-guidelines --skill security-analyst-juniorfontenele

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill proactively identifies and helps you fix security vulnerabilities in your code, preventing potential data breaches and system compromises.

Core Features & Use Cases

Vulnerability Detection: Scans code against OWASP Top 10 and Laravel-specific security flaws.
Severity Rating & Fixes: Assigns severity levels (Critical to Info) and provides actionable recommendations.
Use Case: Before deploying a new feature, run this Skill to ensure no SQL injection, XSS, or broken access control vulnerabilities are present, safeguarding user data.

Quick Start

Analyze the current code changes for security vulnerabilities.

Frequently Asked Questions about security-analyst

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

FAQPage Schema

How do I scan my Laravel code for OWASP Top 10 security vulnerabilities?▼

To scan Laravel code for OWASP Top 10 security vulnerabilities, you can analyze your code patterns against secure coding practices to identify SQL injection, XSS, or broken access control flaws before deployment.

What is the best way to check a pull request for security flaws in PHP applications?▼

Checking a pull request for security flaws involves performing static analysis on the code changes to detect vulnerabilities based on the OWASP Top 10 and framework-specific concerns, providing severity ratings and actionable fixes.

Can I use static analysis to find broken access control issues in my codebase?▼

Yes, static analysis can find broken access control issues by examining code patterns and verifying adherence to secure coding practices, assigning severity levels ranging from Critical to Info to help prioritize fixes.

How do I get actionable fix recommendations for SQL injection vulnerabilities?▼

To get actionable fix recommendations for SQL injection vulnerabilities, run a security analysis that evaluates your code against established standards to detect flaws and provide targeted remediation steps.

When do I need to run a security review on my code changes?▼

You need to run a security review on your code changes before task completion, before submitting pull requests, or whenever you explicitly want to ensure new features do not introduce data breach risks.

Does this security analysis cover framework-specific vulnerabilities or just general OWASP flaws?▼

This security analysis covers both general OWASP Top 10 flaws and framework-specific vulnerabilities, ensuring static analysis of code patterns addresses the unique security concerns of your application architecture.