requesting-code-review

To generate a code review summary for a pull request, run the skill after finishing code changes to automatically compile concise, reviewer-ready briefs from your latest commit and changed files.

Providing context for a code reviewer is done by aggregating task details, changed files via git diff, and success criteria to produce an actionable, reviewer-ready brief you can paste into a PR comment.

Yes, you can automatically compile task details and changed files for a PR comment, as this skill gathers git diff data and task criteria to output a concise changes summary satisfying review requirements.

This code review summary tool works with feature branches and pull requests, applying to changes across them to ensure the reviewer has the necessary context for approval.

You do not need to run git diff manually before preparing a review request, because the skill automatically aggregates changed files and success criteria to compile the reviewer-ready summary.

You should use an automated post-implementation code review summary when you finish implementing a feature and need to reduce context-switching and speed up approvals for your code reviewer.