security-pr-checklist-skill
Creates repeatable security review checklist for PRs with required checks, common pitfalls, and automated gating. Use for "security review", "PR checklist", "code review", or "security gates".
When & Why to Use This Skill
The Security PR Checklist skill streamlines the DevSecOps process by generating standardized, repeatable security review frameworks for pull requests. It helps engineering teams identify critical vulnerabilities—such as hardcoded secrets, SQL injection, and insecure dependencies—before code is merged, ensuring high security standards and automated gating for safer software delivery.
Use Cases
- Standardizing Security Audits: Automatically generate comprehensive checklists for every PR to ensure consistent evaluation of authentication, authorization, and data protection protocols.
- Preventing Data Leaks: Systematically scan code changes for hardcoded credentials, API keys, and PII in logs to prevent sensitive information from reaching production.
- Vulnerability Mitigation: Use structured checks to verify input validation and output encoding, effectively neutralizing common risks like XSS and injection attacks.
- Dependency & CI/CD Integration: Audit third-party packages for known vulnerabilities and establish security gates within the continuous integration pipeline.
| name | security-pr-checklist-skill |
|---|---|
| description | Creates repeatable security review checklist for PRs with required checks, common pitfalls, and automated gating. Use for "security review", "PR checklist", "code review", or "security gates". |
Security PR Checklist Skill
Standardized security review for pull requests.
PR Security Checklist
## Security Review Checklist
### Authentication & Authorization
- [ ] No hardcoded credentials
- [ ] Authorization checks on all endpoints
- [ ] Session management secure
- [ ] Rate limiting on auth endpoints
### Input Validation
- [ ] All inputs validated
- [ ] Output properly encoded
- [ ] No SQL injection risks
- [ ] No XSS vulnerabilities
### Data Protection
- [ ] Sensitive data encrypted at rest
- [ ] HTTPS enforced
- [ ] No PII in logs
- [ ] Secure cookie configuration
### Dependencies
- [ ] No new high/critical vulnerabilities
- [ ] Dependencies up to date
- [ ] No suspicious packages
### Secrets Management
- [ ] No secrets in code
- [ ] Environment variables used
- [ ] .env files in .gitignore
### Error Handling
- [ ] No sensitive info in errors
- [ ] Generic error messages
- [ ] Proper logging
Output Checklist
- PR template created
- Required security checks
- Common pitfalls documented
- Automated checks in CI
- Review guidelines ENDFILE