kiro-review

Spec compliance verification inspects code diffs, runs canonical test suites, and checks for placeholders to ensure task implementations align with approved requirements and boundaries. This review process detects hidden scope creep and silent deviations before acceptance.

Adversarial code review mechanically verifies implementations against approved specifications and task boundaries by running static checks and searching for hardcoded secrets. It prevents scope creep by auditing changed files to detect spillover or hidden dependencies not defined in the spec.

Checking for hardcoded secrets and placeholders involves greping changed files for TODO markers and sensitive strings during the review phase. This mechanical verification ensures implementations contain real logic rather than unfinished fragments before approval.

Static analysis and boundary audits should run after an implementer reports READY_FOR_REVIEW, after remediation, or before marking a task complete. This timing ensures all code changes are mechanically verified against design constraints prior to higher-level validation.

Automated review generates structured APPROVED or REJECTED verdicts by comparing changed files to task boundaries, running validation commands, and auditing design alignment. The verdict includes specific findings and remediation steps for rejected work.

Auditing task boundary adherence requires comparing changed files to task Boundary constraints and referenced design sections to detect spillover. This review confirms implementations stay within approved scope and avoids hidden dependencies before final acceptance.