quality-gate

To automate code review for a pull request, you trigger six parallel evaluators that vet diffs for correctness, performance, security, and other facets. It aggregates a trust score to block risky merges before commit.

A trust score threshold for blocking risky code changes is 80 or above. When the aggregated score from the six evaluators meets this threshold, the quality gate blocks the change and routes the flow to fix the issues.

You can run parallel code reviews on a specific directory scope by configuring the evaluator target. The quality gate defaults to analyzing diffs only, but supports all-files or specific directory scopes to fit various workflows.

Yes, the quality gate works with TDD workflows by integrating with tdd-review. It enforces automation gates during development by aggregating review scores and routing the flow to either commit or fix the code.

Aspects of code changes evaluated during an automated quality gate include correctness, performance, security, guidelines, product impact, and usability. Six specialized agents review these facets simultaneously to surface issues before merging.