review-checklist

To catch recurring code review issues before merging, apply a standardized pre-merge checklist that verifies transactional database updates, redacts sensitive parameters from logs, and validates network targets to prevent SSRF. This enforces review discipline across database safety, security, and test hygiene.

A pre-merge checklist for database operations and test hygiene should verify that destructive actions require approval, transactional DB updates are enforced, and unit tests use safe temp handling with mocks instead of real network calls to prevent global state mutation.

To prevent prompt injection and credential leakage during security review, validate untrusted data boundaries and ensure sensitive parameters are redacted from logs and broadcasts before merging any security-sensitive tooling changes.

Yes, a review checklist applies to Rust trait wrapper chains and unsafe string or path handling by verifying correctness across high-frequency failure modes and ensuring destructive actions require explicit approval before integration.

To apply a review checklist to your pull request, ask the AI to run the verification using a phrase like review checklist, then confirm each item with evidence directly from the changed files to ensure all safety and security criteria pass.