ck:code-review

To verify code quality before a pull request, run an orchestrated scout, review, fix, and verify pipeline. This enforces edge-case scouting and technical rigor to catch boundary conditions and side effects before completion claims are accepted.

The best way to orchestrate code reviews for multi-file changes is using a task-managed pipeline that dispatches parallel review and re-review cycles. This ensures comprehensive verification across all modified scopes without missing unscoped impacts.

To prevent performative agreement during a code review, enforce an evidence-first protocol that applies YAGNI, KISS, and DRY principles. This replaces superficial approvals with explicit verification gates requiring fresh test or build evidence.

No, you cannot claim a task is done without fresh verification evidence. A completion verification gate blocks any passing or fixed claims until you produce current proof from tests, builds, or requirement checks.

You need to run an edge-case scouting gate during post-feature implementation checks or pre-PR reviews. It proactively identifies boundary conditions and side effects before dispatching a code reviewer, ensuring technical correctness.