Requesting Code Review

A dedicated code reviewer checks your work before you merge changes. It focuses only on the code you built, not your entire session history. This keeps reviews fast and objective. Review early and review often to catch issues before they grow.

You can request a review after each task or before merging to main. The reviewer gets clear context about what you built and what it should do. It returns strengths and issues for you to fix. Critical issues must be fixed right away. Important issues must be fixed before moving on. Minor issues can wait.

This skill helps developers ship better code with less rework. It works well in subagent-driven development, plan execution, or ad-hoc projects. Use it whenever you want a fresh pair of eyes on your code.