pre-push-check

To run automated code review checks before pushing, execute the pre-push pipeline which validates your git diff by performing a self-review against CLAUDE.md and screening for common issues like secrets or missing tests. This enforces project quality gates before changes reach the main branch.

A pre-push quality gate is an automated validation checkpoint preventing broken commits from reaching the main branch. It enforces compliance by verifying scope discipline, architecture patterns, and security against the rules defined in your CLAUDE.md file.

Yes, you can use pre-push checks for staging and release workflows. They are specifically designed for environments requiring consistent quality gates, fast feedback, and reduced regression risk across diffs before integrating changes into upstream branches.

During a pre-push self-review, the pipeline flags risky or low-quality commits such as hardcoded secrets, leftover debug logs, `any` type usage, missing async error handling, and TODOs without ticket references to ensure clean, secure code.

If the primary Claude Code tool fails during the pre-push check, the pipeline automatically falls back to OpenCode, and subsequently to direct lint and type-check fallbacks. This ensures your diff-based self-review and issue screening still execute successfully.