security-review

Run a security review on code changes by prompting Claude to assess the specified modules or PRs, which produces a prioritized findings report. This surfaces risks across sensitive code paths like authentication, payments, and user data before production deployment.

An automated security check covers authentication and authorization checks, input validation, data exposure minimization, secrets management, API endpoints, and deployment pipeline configurations. It also scans for hardcoded keys and vulnerable dependencies.

Perform a security review on APIs and deployment pipelines before merging changes that affect sensitive code paths or alter configurations. This ensures compliance with security best practices and prevents vulnerabilities from reaching production.

Yes, code review can detect hardcoded secrets and vulnerable dependencies through dedicated scanning. It identifies exposed keys and unsafe libraries, providing recommended fixes to ensure secure storage and safe dependency usage.

The best way to check input validation and data exposure is applying an automated security checklist to your modules. This systematically assesses whether minimal data is exposed and inputs are properly validated against security best practices.

Yes, this security review supports authentication and authorization checks across different projects and PRs. It evaluates access controls and compliance with security best practices regardless of the specific project scope.