security-review

Run a security review on a pull request by triggering the skill on your current branch. It evaluates code changes for vulnerabilities, auth boundaries, and secret leaks, then generates a findings report with remediation steps.

OWASP vulnerability scanning for code changes identifies security gaps in authentication, authorization, and external integrations. It applies checklist-driven evaluation to ensure inputs are validated and secrets are prevented from leaking before merging.

Yes, you can check authorization boundaries in your current branch. The review enforces per-instance scoping and validates data access controls across changes touching auth, payments, or external APIs without needing a full security audit.

Yes, this security review covers file uploads and external API integrations. It provides actionable remediation guidance for these external integrations, validating inputs and checking for policy gaps within your scoped code changes.

The best way to prevent secrets leakage before merging is a focused code review of changes touching secret management. This process enforces checklist requirements to detect vulnerabilities and documents clear remediation steps for any detected leaks.

You need a focused security review instead of a full audit when evaluating specific code changes on a branch or PR. It delivers fast feedback on authentication, data access, and payments without scanning the entire codebase.