unified-commit-gate

To enforce quality gates before a git commit or push, you can run a unified commit gate that executes lint, style, code review, language, and IP audits on your repository files. This prevents flawed commits and accidental proprietary leaks.

Yes, you can run an IP audit on public remotes before pushing code. The unified commit gate performs this audit during the push phase to prevent accidental leaks of proprietary information to external repositories.

You can automate lint and code review checks before committing by invoking a unified commit gate with a slash command. It executes linting, type checking, and dispatches an adversarial code review for your code and documentation.

Yes, the commit gate quality check requires access to shell utilities like shellcheck. It needs these utilities and internal scanning scripts to properly enforce shell script style guidelines and execute comprehensive repository file audits.

A sentinel check for code review clearance is a safeguard included in a unified commit gate to ensure all adversarial code reviews are fully passed. It acts as a final blocker before allowing any code to be pushed to a remote repository.