security-audit

You can automate security audits for pull requests by invoking a security-analyst-specialist agent that analyzes changed files for vulnerabilities and formats findings directly into PR comments.

An automated PR vulnerability analysis checks changed files for injection risks, authentication weaknesses, data exposure, architectural layering concerns, and adherence to security best practices.

To scan code for PII exposure and compliance issues during code review, trigger a data-integrity scan that surfaces regulatory considerations and formats them into a structured PR report.

No additional dependencies are required to run a data-integrity scan, as the security audit tool coordinates the security-analyst-specialist and compliance checks internally without external components.

The best way to review architectural concerns across multiple changed modules is running a security audit that validates proper layering, input validation, and test coverage gaps to return a structured report.

You should avoid using automated security audits when a pull request contains non-code changes, as the vulnerability analysis and data-integrity scans target code, tests, and deployment configurations specifically.