security-review

Security best practices for code review include checking input validation, authentication, authorization, secrets management, and rate limiting. This skill provides a comprehensive checklist, example patterns, and validation rules to systematically identify vulnerabilities and enforce safe defaults across code and APIs.

You can integrate automated security checks into pull requests by running this skill against new feature branches. It evaluates code changes against security checklists and generates actionable remediation guidance to help developers apply fixes and reduce risk before merging.

To prevent secrets from leaking in deployment configurations, apply strict secrets management validation rules provided by this skill. It offers practical patterns and secure configuration templates to ensure sensitive data is handled safely across your cloud infrastructure and CI/CD workflows.

Yes, this security review covers API design and input validation comprehensively. It guides developers through specific checks and safe defaults for input handling, ensuring that APIs enforce proper authorization, rate limiting, and data sanitization before processing requests.

The best way to harden code for cloud infrastructure and payments is to apply comprehensive security checks targeting these specific domains. This skill enforces secure configuration patterns, validates authorization controls, and provides deployment hardening rules to protect sensitive payment flows.

You should not rely solely on automated vulnerability scanning when you need contextual design-level security enforcement. While scanning finds known flaws, this skill provides deeper analysis by evaluating architectural patterns, API design choices, and safe defaults to guide comprehensive remediation.