Request Code Review
Give reviewers a precise packet that separates proposed code from checks, decisions, deployment, and merge authority.
Workflow
- Verify repository identity, base and head branches, exact revision, diff scope, and unrelated changes.
- Summarize the problem, chosen approach, user-visible or contract impact, and excluded work.
- Record checks by exact command and result. Name tests or environments that were not run.
- Identify security, data, compatibility, migration, operational, and rollback risks.
- Provide a short review focus with concrete questions and high-risk files or paths.
- Confirm whether the user authorized only preparing the packet or also sending it through a named external channel.
- After an authorized send, read back the created request, URL, revision, reviewer state, and checks.
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
Return Scope, Approach, Evidence, Risks, Not tested, Review focus, Authority, and, if sent, External readback.
1---2name: request-code-review3description: Prepare an evidence-bounded code review packet and, only when separately authorized, send or publish the request. Invoke explicitly when a change is ready for reviewer attention and its scope, checks, risks, and unresolved decisions must be stated precisely.4license: MIT5---67# Request Code Review89Give reviewers a precise packet that separates proposed code from checks, decisions, deployment, and merge authority.1011## Workflow12131. Verify repository identity, base and head branches, exact revision, diff scope, and unrelated changes.142. Summarize the problem, chosen approach, user-visible or contract impact, and excluded work.153. Record checks by exact command and result. Name tests or environments that were not run.164. Identify security, data, compatibility, migration, operational, and rollback risks.175. Provide a short review focus with concrete questions and high-risk files or paths.186. Confirm whether the user authorized only preparing the packet or also sending it through a named external channel.197. After an authorized send, read back the created request, URL, revision, reviewer state, and checks.2021## Boundaries2223- Explicit invocation does not by itself authorize push, PR creation, reviewer assignment, external messaging, merge, or deployment.24- Do not describe a check as passing from stale output or a different revision.25- A review request is proposed work, not approval or merge authority.2627## Output2829Return `Scope`, `Approach`, `Evidence`, `Risks`, `Not tested`, `Review focus`, `Authority`, and, if sent, `External readback`.
JovaniPink