review-changes

Run a pre-commit security review on your git diff to analyze staged, unstaged, and untracked files for vulnerabilities. The review assigns risk tiers to changed files and blocks commits when critical security findings are detected.

Risk-tiered file classification evaluates uncommitted changes by assigning each file a CRITICAL, HIGH, MEDIUM, or LOW tier based on its blast radius across security areas like auth, crypto, and data access logic.

Prevent secrets and SQL injection vulnerabilities from being committed by running a two-pass review on your git changes. The first pass blocks commits on critical findings like injection vectors and hardcoded secrets.

Yes, you can check removed code for relaxed security guards. A removed-code audit investigates deleted lines in high-risk tier areas using git history to determine if security protections were weakened or removed.

The code review process catches insecure fail-open patterns, concurrency issues, and TOCTOU race conditions. It performs a second informational pass to report these breadth checks alongside test gaps and debug leftovers.

Use a pre-commit code review instead of a standard linter when you need to analyze uncommitted git diffs for deep security vulnerabilities and correctness bugs in critical areas like authorization and boundary validation.