requesting-code-review

Automating pull request code review prompts involves generating standardized templates that capture implemented changes, plan alignment, and commit ranges. This skill creates structured feedback artefacts ready to paste into PRs or chat channels for teammates.

A standardized code review template for Git repositories is a structured prompt outlining what was implemented, base and head SHAs, and requirements alignment. It ensures consistent feedback by providing a clear format for evaluating changes before merges.

Generating pre-merge review feedback requires providing the base and head Git SHAs along with a short description of changes. The workflow produces a shareable report detailing implemented updates and plan alignment for feature work validation.

Yes, you can use this code review template for task-driven development cycles. It triggers reviews after each task and during refactoring, applying standardized prompts across Git repositories to catch issues early before merges.

Structuring code review feedback for chat channels requires a standardized template including implemented changes, commit range, and plan alignment. This approach produces a ready-to-share report artifact that integrates smoothly into PR workflows.

Yes, you need to provide base and head Git commit SHAs to trigger the code review workflow. Supplying these SHAs along with a change description allows the template to accurately track and evaluate the specific commit range.