# Request Review

> Prepares a review packet when explicitly asked to request review of a change; states scope, tests, and risks, and sends it only when the destination and action are authorized.

- Skill: `jovanipink/request-review` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx get-skill add jovanipink/request-review`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jovanipink/request-review/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: JovaniPink (https://skillmd.com/u/jovanipink)
- Updated: 2026-11-15
- Page: https://skillmd.com/skills/jovanipink/request-review

---


# Request Code Review

Give reviewers a precise packet that separates proposed code from checks, decisions, deployment, and merge authority. `publish-change` owns the commit, the push, and the pull request record. This workflow owns the reviewer-facing content and its authorized delivery. When a request also asks to publish the change, route the commit and push to `publish-change` and keep the packet here.

## Workflow

1. Verify repository identity, base and head branches, exact revision, diff scope, and unrelated changes.
2. Summarize the problem, chosen approach, user-visible or contract impact, and excluded work.
3. Record checks by exact command and result. Name tests or environments that were not run.
4. Identify security, data, compatibility, migration, operational, and rollback risks.
5. Provide a short review focus with concrete questions and high-risk files or paths.
6. Confirm whether the user authorized only preparing the packet or also sending it through a named external channel.
7. After an authorized send, read back the created request, URL, revision, reviewer state, and checks.

## Review identity and coverage

A packet for uncommitted work includes relevant staged, unstaged, and untracked
files as well as base/head revisions. Bind relevant file contents with path and
SHA-256, labeling index, working-tree, and untracked representations. Retain both
versions when the same path differs in the index and working tree, plus deletions
and file modes; exclude unrelated or sensitive files.
A committed diff alone cannot represent that working tree. Recheck the snapshot
before sending and reconcile any concurrent changes.

For repeated review, retain stable finding IDs and prior dispositions. Report the
reviewed revision or snapshot, review mode, actual reviewer identity when known,
rounds consumed and remaining, unresolved findings, and coverage limits. Do not
turn self-review into an independent-review claim or a model verdict into human
approval. Preparing this packet does not launch a reviewer or send a request.

## Boundaries

- Explicit invocation does not by itself authorize push, PR creation, reviewer assignment, external messaging, merge, or deployment.
- Do not describe a check as passing from stale output or a different revision.
- A review request is proposed work, not approval or merge authority.

## Output

Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.

Return `Scope`, `Approach`, `Evidence`, `Risks`, `Not tested`, `Review focus`, `Authority`, and, if sent, `External readback`.

## Example

Synthetic example; not an observed client result.

Input: Prepare a review request for a tested patch; sending it is not authorized.

Output: The packet states the patch scope, revision, tests, and open risks. It is prepared locally and has not been sent.

