requesting-code-review

Pre-commit security scans identify hardcoded secrets and common vulnerabilities by executing static analysis tools on file diff changes before code is committed. This prevents sensitive data leaks and ensures secure code enters the repository.

A two-stage code review pipeline separates code implementation from the review process by executing independent reviewer subagents. This unbiased analysis enforces coding standards, applies quick fixes, and re-verifies changes to prevent regressions.

Yes, automated static analysis and quality checks are applicable to code repositories and automated pipelines. The skill processes file diff changes and integrates into environments requiring secure, quality-assured code verification before deployment.

The auto-fix loop prevents regressions by applying quick fixes and re-verifying code changes during the verification pipeline. This automated cycle ensures that applied fixes do not introduce new vulnerabilities or break existing coding standards.

Static analysis and linting are needed for code commits when enforcing coding standards and identifying security vulnerabilities before changes enter the main branch. This pre-commit verification ensures high-quality, secure code in automated pipelines.