requesting-code-review

Automating pre-commit security checks uses static analysis to detect hardcoded secrets, shell injections, and unsafe deserialization before code is committed. This skill enforces that automated pipeline to block vulnerabilities from entering the codebase.

An independent subagent review uses a secondary, isolated AI agent to perform a logic and security audit on your git diff. It provides a fail-closed verdict to ensure high code quality and security compliance before merging changes.

Automated pre-commit code verification works with standard language-specific test runners and linting tools. You must have git, these testing frameworks, and linting tools present in your development environment to execute baseline-aware regression testing.

Preventing regressions and security vulnerabilities before merging requires running baseline-aware test suites and automated security scanning. This skill enforces an independent verification pipeline that blocks commits introducing hardcoded secrets or unsafe patterns.

The limitations of automated pre-commit code review include strict dependency on existing local environments; it requires git, standard language-specific test runners, and linting tools to be pre-configured, meaning it cannot execute verification in environments lacking these baseline utilities.