fresh-eyes-review

A final sanity check before release identifies and discloses security vulnerabilities, logic errors, and business-rule bugs that slip past automated tests and peer review. It enforces a structured checklist for security, correctness, and business rules.

To catch business-rule bugs and logic errors before committing, re-read touched files using a structured checklist. This surfaces logical defects and inconsistencies after implementation, ensuring correctness before a git commit.

You do not need special tooling to perform a release check on changed files. The review requires only the project context and enforces a structured checklist for security and correctness without additional dependencies.

The best way to surface security vulnerabilities missed by automated tests is applying a fresh-eyes review after implementation. It re-reads touched files to catch common vulnerabilities and logical defects before a release declaration.

You should use a manual code review checklist instead of automated tests when you need a final quality gate before a PR. It catches business-rule inconsistencies and security vulnerabilities that automated testing logic often misses.