source-command-evaluate

You can automate code evaluation against a predefined specification by running an automated review command with your plan file path. This performs contract-based grading and adversarial reviews to ensure implementation adherence without manual checks.

An adversarial code review is a parallel validation process that challenges design assumptions and identifies potential failures in an implementation. It ensures code quality by actively trying to break the code against a predefined contract before merging into the main codebase.

To run contract-based testing on a codebase before merging changes, execute the evaluation command with the path to your plan file. This automatically validates the code diff against the contract and provides feedback on any specification adherence issues.

Yes, you need a plan file to perform automated code review because it defines the contract used to grade the implementation. The evaluation process requires this plan file, along with the codebase, to execute code diffing and validation commands.

Yes, you can use automated code review to eliminate bias in pull request evaluations by grading implementations against a predefined contract. This ensures objective quality standards are met and removes human subjectivity from the code review process.

The limitation of contract-based code evaluation is that it cannot review code without a predefined plan file specifying the contract. It also relies entirely on the ability to execute code diffing and validation commands, requiring access to the codebase environment.