security-permissions-review

To scan code changes for security vulnerabilities before deploying, use a pre-deploy review process that checks git diffs modifying authentication, permissions, secrets, and production data surfaces. This prevents unauthorized access and data exposure by enforcing least-privilege checks.

Secret redaction in environment files and deploy configurations works by scanning code diffs for sensitive data and automatically masking or removing exposed secrets. This prevents potential secret leaks from reaching production environments during deployment.

An approval gate in code security reviews is an enforcement mechanism that identifies operations requiring formal authorization and surfaces missing approval artifacts. This blocks unauthorized deploys by validating that all required permissions are verified before code changes are pushed.

To check for missing auth validation in new endpoints, scan the git diff for changes to auth middleware and database write operations. The review flags missing authentication checks and permission gaps to prevent unauthorized access to customer data flows.

Yes, you can use a security review skill for database write operations and customer-facing data flows. It automatically flags changes to outbound customer-facing messages and database operations, catching missing permission checks and potential data exposure risks.

You need a least-privilege permission check for production data handling when code changes touch sensitive surfaces like auth middleware, environment files, and database operations. This prevents compliance violations and data breaches by ensuring access is appropriately restricted.