kiro-review

Boundary-aware code review verifies that a task implementation stays within the approved boundary by comparing changes against the spec and design, and confirms evidence from mechanical validation checks.

To verify spec compliance after implementation, compare the code diff and status report against the requirement and design sections, execute validation commands, and generate a formal verdict with findings.

You need to perform a regression safety and boundary check after an implementer finishes work, after remediation, or before task acceptance to ensure the changes satisfy requirements without exceeding approved boundaries.

The best way to review task changes is to mechanically diff the code modifications and status reports against the relevant requirement and design sections, verifying validation evidence to produce a structured verdict with remediation steps.

Yes, you can use mechanical validation to diff code changes and status reports, identifying whether the implementation stays within the approved boundary and satisfies the verification criteria from the spec.

To perform a rigorous task review, you need the task ID, relevant requirement and design sections, file paths, status reports, and validation commands to verify spec compliance and boundary safety.