security-review-pr

You can audit a pull request diff for security issues by applying a dedicated review skill that automatically surfaces input validation flaws, authentication gaps, and secrets handling problems directly within the code changes.

Yes, you can integrate security findings into your code review workflow by folding the identified vulnerabilities into a shared review.json file, maintaining a single source of truth for reviewers without posting automatic comments.

A pull request security review typically checks for input validation and sanitization flaws, broken authentication and authorization checks, secrets management issues, and unsafe dependencies introduced in the diff.

Automated security review does not post comments directly to the pull request; instead, it consolidates findings and guidance into an existing review.json file to avoid cluttering the PR with automatic comments.

To check for risky dependencies when reviewing a code PR, apply a security audit skill that identifies unsafe dependencies alongside input validation and authorization issues, merging the results into a single review output.