requesting-code-review

Automating pre-commit code reviews for security and quality is done by running this skill on your local git repository. It scans for hardcoded secrets, runs tests and linters, and uses an independent subagent to ensure your changes meet predefined standards before merging.

Scanning your code for hardcoded secrets and shell injection vulnerabilities is handled by the security scan feature during the pre-commit review process. It identifies these security flaws along with other vulnerabilities before your code is committed.

Yes, you can automatically fix code quality issues using the built-in auto-fix loop. It offers automatic fixes for certain problems detected by the linters and security scans, running for up to two cycles to resolve the identified issues.

Pre-commit automated testing works with your existing external tools by requiring access to them for running tests and linting. It integrates with your local git repository setup to enforce quality gates and ensure functionality before merging.

An independent subagent performs an unbiased code review by evaluating your local git changes separately from the primary development process. This ensures an objective assessment of security and quality standards before the code is committed.

The limitations of an automated pre-commit review include a maximum of two auto-fix cycles for certain issues. It also requires access to the local git repository and external testing tools to function properly during collaborative code changes.