review

You can check code changes against implementation specifications and coding standards by running a two-axis review that analyzes commit history against specification documentation using parallel sub-agents to prevent context contamination.

A two-axis code review evaluates changes along two parallel tracks: coding standards and implementation specifications. It uses parallel sub-agents to review each axis independently, preventing context contamination and ensuring thorough specification compliance.

To review a pull request branch against specification documentation, provide the commit history and specification files. The review process checks implementation compliance and coding standards simultaneously using isolated sub-agents.

Yes, commit history and specification documentation are required to run this code review. The two-axis review requires access to both to evaluate whether code changes adhere to implementation specifications and coding standards accurately.

Using parallel sub-agents for code review avoids context contamination. By running standards compliance and specification checks independently, each sub-agent maintains focused context, resulting in a more thorough and accurate review of code changes.

Yes, you can review code changes starting from a specific commit hash. By providing a starting commit like 'abc123', the review process analyzes all subsequent changes against coding standards and implementation specifications.