requesting-code-review

Automated pre-commit security checks scan your git diff for hardcoded secrets, shell injections, and unsafe deserialization patterns. This skill enforces a verification pipeline that runs static security analysis and quality gates before any code enters the repository.

Baseline-aware test regression checks run your test suites and linting tools to ensure new code changes do not degrade existing project quality. They compare new test results against the established project baseline to prevent regressions from being committed.

Yes, an independent reviewer subagent can audit your git diff. This skill employs a secondary, isolated AI agent to perform a fresh logic and security review on your changes, providing an automated quality assurance perspective before commit.

Yes, terminal access is required to execute automated pre-commit code review. The process needs to run git commands, language-specific test runners, and static analysis tools directly within your software development environment.

Automated pre-commit verification detects unsafe code patterns by performing real-time static security analysis on your changes. It identifies hardcoded secrets, shell injections, and unsafe deserialization to prevent vulnerabilities from entering your codebase.