review-code

Adversarial code review verifies implemented code against the original plan, identifying bugs, security vulnerabilities, and performance issues. It rigorously checks code quality and adherence to acceptance criteria before allowing progression to subsequent development phases.

Adversarial code review critically examines executed code phases to verify implementation against the plan and identify bugs. It requires git commands for state checking and performs detailed analysis of code quality, security vulnerabilities, and adherence to acceptance criteria.

Yes, you can verify acceptance criteria after an executor agent implements code. The review process critically examines the latest commits, confirms that all specified requirements from the plan have been met, and flags any implementation mismatches for revision.

Yes, git is required to perform implementation verification. The review process uses git commands for state checking to accurately assess the latest commits, verify code quality, and enforce gatekeeping between execution and subsequent development phases.

Automated code review for bug detection is limited to analyzing executed code phases and requires a pre-defined plan with acceptance criteria. It functions as a quality gate between execution and subsequent phases, meaning it cannot review unexecuted or unplanned code changes.