requesting-code-review

Automated code review before committing changes involves running static analysis and linting tools to detect security vulnerabilities and quality regressions. This process uses a subagent to perform an independent review and apply baseline-aware quality gates to your repository.

A pre-commit security scan is an automated check that detects hardcoded secrets, shell injection, and other vulnerabilities in your code. It runs static analysis before changes are committed, ensuring no new security issues are introduced into the repository.

Yes, you need a git repository to track changes, along with static analysis, linting, and testing framework tools. These dependencies are required to scan for security vulnerabilities, lint code, and run baseline tests to identify regressions.

Baseline-aware quality testing works by running tests against a known baseline to identify regressions during code review. It compares new code changes with existing test results, ensuring that recent modifications do not break current functionality or introduce quality issues.

The best way to prevent quality regressions when pushing code is to execute an automated pre-commit verification process. This involves linting code, running baseline tests, and using an independent reviewer subagent to ensure no quality issues or security vulnerabilities are introduced.