---
name: code-review-request-packager
description: "Packages a change for a reviewer with its scope, the best place to start looking, how it was tested and the gaps you already know about. Use when a finished change is about to go up for review and needs a clear request that tells the reviewer where to look. Do not use for answering review comments already received or writing the pull request title and body. Related topics: coding, communication."
---

# Code Review Request Packager

Packages a change for a reviewer with its scope, the best place to start looking, how it was tested and the gaps you already know about.

## When to use

Use this skill when a finished change is about to go up for review and needs a clear request that tells the reviewer where to look. Do not use it for answering review comments already received or writing the pull request title and body.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Summarise the purpose and visible effect in one paragraph from the change summary and diff.
3. Define scope in and out, so the reviewer knows what is intentionally missing.
4. Give a reading order that names the first files to open and marks mechanical files as skippable.
5. Report tests run and results and state plainly what was not tested.
6. List known gaps and the specific questions where the reviewer's judgement is needed.

## Inputs

- **Change summary** (longer free text)
- **Diff or file list** (longer free text)
- **Tests run** (longer free text)
- **Risk areas** (longer free text)
- **Reviewer** (choose one: Teammate who knows the code, Teammate new to the code, Outside maintainer)
- **Review size** (choose one: Quick skim, Careful read, Deep audit)

## Output

A one-page review request with sections for purpose, scope, reading order, testing, known gaps and questions for the reviewer.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Code Review Request Packager

Prepare this change for review so a reviewer can start in the right place.

- Change summary: {{Change summary}}
- Diff or file list: {{Diff or file list}}
- Tests run: {{Tests run}}
- Risk areas: {{Risk areas}}
- Reviewer: {{Reviewer}}
- Review size: {{Review size}}

Write the request in this order. One paragraph on the purpose and the user-visible effect. The scope: what is in this change and what is deliberately left for later. A reading order: the two or three files to open first and why, then the rest grouped by role, with generated or mechanical files marked skippable. How it was tested, with commands and what each showed, plus what was not tested. Known gaps, shortcuts and follow-ups, stated honestly. Specific questions where the reviewer's judgement is wanted, such as a naming or a trade-off. Pitch the amount of background to the chosen reviewer, and keep the whole request under one page.

## Pitfalls

- Dumping the whole diff without a reading order, so the reviewer spends the first half hour finding the point.
- Hiding known shortcuts, which a reviewer then finds and trusts the rest less.
- Listing tests run without results, which leaves the reader unable to tell passing from attempted.