requesting-code-review

To run a pre-commit code review and security scan, use this Skill to automatically detect hardcoded secrets, SQL injection, and logic errors in your staged changes. It enforces quality gates by validating security rules and blocking commits if vulnerabilities are found.

Yes, you can automatically fix security vulnerabilities and test regressions before committing code. The Skill spawns a dedicated auto-fix agent that resolves detected issues, running a maximum of two fix-and-reverify cycles to prevent infinite loops.

To prevent new code changes from introducing lint or test regressions, the Skill performs baseline-aware quality checks. It compares your test and lint results against pre-change baselines to flag only new regressions, avoiding false positives from pre-existing issues.

Pre-commit static analysis does detect shell injection risks, hardcoded secrets, unsafe eval/exec calls, and SQL injection patterns. It scans added code lines during your git verification workflow to ensure high-quality, secure commits.

Independent subagent code review works by using a separate, context-isolated reviewer agent to catch logic errors the implementer missed. It applies strict fail-closed rules that block git commits for any detected security or logic problems.

The best way to enforce security rule validation in a pre-commit workflow is to use an automated verification Skill. It applies static security scans, regression detection, and a bounded auto-fix loop to satisfy requirements for secure, high-quality code commits.