requesting-code-review

Request code review by identifying your commit range and dispatching a code-reviewer agent with context about your changes, focus areas, and rationale. This skill automates that process after you complete self-review, ensuring reviewers have all necessary details for faster, more effective feedback.

Implement a formal review protocol that enforces self-review before external review, identifies relevant commits, and uses standardized request templates. This reduces reviewer burden, catches issues early, and accelerates the merge cycle by providing clear context upfront.

Code review requests should capture commit ranges, focus areas, changes summary, and explicit rationale for your feature or fix. This skill generates detailed contextual requests automatically, guiding reviewers on what to prioritize—security, performance, test coverage—and reducing back-and-forth delays.

Perform self-review immediately after completing a feature or major change and before requesting external review. This mandatory step improves initial quality, catches obvious issues, and ensures external reviewers focus on substantive feedback rather than basic problems, speeding up the overall review cycle.

Yes. This skill automatically identifies commit ranges for your feature branch and generates a structured review request with all relevant context. It dispatches the request to a code-reviewer agent, eliminating manual prompt writing and ensuring consistency across your development workflow.

Self-review is your initial quality check on your own code before merge; external code review is a peer or agent reviewing after. This skill enforces both sequentially—self-review first catches gaps, then external review provides fresh perspective on security, performance, and test coverage.