requesting-code-review

To run a pre-commit code review, initiate a check that performs static analysis, scans for hardcoded secrets, and assigns an independent subagent to review functional correctness before committing changes.

An independent code review assigns an isolated subagent to assess code changes for impartiality. It evaluates security, quality, and functional correctness before changes are committed to a version-controlled repository.

Yes, an auto-fix loop automatically addresses identified security and quality concerns, re-verifying the code against baseline tests and linting results to ensure issues are resolved pre-commit.

Pre-commit static analysis includes a security scan specifically designed to check for hardcoded secrets and potential security vulnerabilities within your code changes before they reach the repository.

The best way to verify baseline tests and linting is to compare current changes against baseline results and run appropriate linters, ensuring code meets quality standards before an independent review.

You should avoid automated code review if your changes require complex contextual understanding beyond static analysis, as it focuses on pre-commit security, linting, and functional correctness checks.