create-run-gates

You can run local CI validation gates before a pull request by executing the repository gate runner against your current working tree to evaluate code analysis and repository compliance checks.

Pre-PR checks to catch CI failures locally include running blocking and advisory validation gates for documentation, graph, hygiene, and style violations to ensure repository compliance before submitting code.

Yes, you can verify code analysis and repository compliance locally by running the same validation gates used by the CI pipeline against your current working tree before pushing code.

Local pre-PR verification detects both blocking and advisory issues by consistently applying repository gate runner checks to identify documentation, graph, hygiene, and style violations before review.

If changes pass locally but fail remote CI validation, running the same code-analysis gates used by the pipeline against your working tree ensures consistency and identifies blocking issues before submission.

The best way to automate working tree validation for GitHub repository checks is to execute the local CI gate runner, which applies pre-PR code analysis and hygiene verification consistently with pipeline rules.