vcp-pre-commit-review

To enforce code quality and security standards before a commit, you can analyze staged files against VCP rules to produce a PASS or BLOCK verdict. This pre-commit review mechanism loads project configurations, filters findings with ignore rules, and outputs structured results.

Yes, you can integrate pre-commit code review checks into your CI pipeline. The review process outputs a structured global PASS or BLOCK verdict with per-file severity findings, which is specifically designed for automated workflows and CI integration.

Pre-commit validation handles multi-file changes across varied languages by analyzing the entire current commit set. It resolves configuration via a dedicated pluginRoot, loads all applicable VCP standards dynamically, and applies them uniformly to produce a global compliance verdict.

Yes, you need a .vcp/config.json configuration file to manage ignore rules during a pre-commit code review. This config-driven approach allows the review process to respect your ignore rules and tailor findings specifically to your project requirements.

The best way to block non-compliant code locally is to run a pre-commit review that analyzes staged changes against VCP standards. It generates a BLOCK verdict if violations are found, preventing the commit until the reported per-file findings are resolved.

A pre-commit review reports a BLOCK verdict because it analyzes all staged or changed files against applicable VCP standards, not just individual line counts. It aggregates per-file severity findings into a global decision, meaning any unresolved violation triggers a block.