requesting-code-review

You can automate pre-commit code review by running a workflow that analyzes git diffs, executes static security scans, linting, and baseline tests, then proposes auto-fixes before code enters the codebase.

An independent reviewer subagent coordinates two-stage verification to avoid self-review bias during code quality checks. It independently evaluates the diff and static analysis results to ensure rigorous, unbiased verification before committing changes.

Running static security scans on git diffs requires extracting the changed code and applying automated quality gates. This skill executes those security checks directly on feature branch diffs to surface risks before commits are finalized.

Yes, you can use an auto-fix loop for pre-commit linting and testing to suggest or apply fixes for common issues automatically. This process maintains a safe, auditable history while ensuring code meets baseline quality standards before landing.

Yes, pre-commit verification workflows support feature branches, commits, and pushes. The skill applies static checks, baseline comparisons, and multi-agent coordination directly to the branch diffs to mitigate risks before code lands.

Automated pre-commit code review is limited to catching static issues, linting errors, and security risks present in the diff. While it proposes auto-fixes for common problems, it may not detect complex architectural flaws or runtime logic errors.