What problem does it solve? Final code review of a BeeUI implementation requires reconciling the approved Issue, the actual diff, SDLC and security rules, and verification evidence before a PR can be approved or sent back for corrections. This Skill enforces a strict, read-only, multi-phase review workflow so no acceptance criterion, changed file, or blocker is missed. ## Core Features & Use Cases - Phased review gates: Resolves GitHub Issue/PR context, verifies exact instruction and target worktrees and branches, consumes the complete review manifest and paginated diff, and reads every changed and related file before issuing findings. - Consolidated verdicts: Returns exactly one outcome — approval with a PR body and squash commit recommendation, a blocker list with exact before/after corrections, or an incomplete-review notice when data is missing. - Correction prompt generation: Produces a consolidated, executor-ready correction prompt scoped to the target worktree with required verification steps. - Use Case: After a BeeUI feature branch is implemented and verified, run this workflow to confirm every Acceptance Criterion, detect real blockers such as contract violations or unrelated files, and produce the final PR close package. ## Quick Start Review the BeeUI implementation in the target worktree against the approved Issue and base branch, then return the final verdict and PR close package.
