evaluator

To evaluate code against a Sprint Contract, load the contract and audit inputs to identify criteria, then process changed files and run checks to produce a PASS/FAIL verdict with a calibrated score.

A Sprint Contract in code review defines the evaluation criteria used to score implementations, ensuring QA testing objectively measures changed files against expected project standards and remediation guidance.

Run the evaluator with your Sprint Contract and list of changed files to generate a structured critique, executing checks that deliver a decision report with actionable feedback for iteration.

Yes, you can calibrate QA scoring by providing previous evaluation inputs alongside the Sprint Contract and changed files, allowing the evaluator to compute objective scores and track remediation trends.

The best way to generate structured code review reports is to apply an evaluation protocol that assesses testability and executes checks, yielding a verdict, score, and actionable remediation guidance.

A code review evaluation returns a FAIL verdict when changed files are calibrated against the Sprint Contract criteria and fail specific testability checks, requiring iteration based on the generated remediation guidance.