1. Critique before publishing.
Inspect repository and environmental evidence, then classify feedback as blocker, material risk, suggestion, question, or positive observation.
A launch team reads a rendered PR, questions the rollback plan, and asks an agent for a focused revision. Follow the decision from Inbox through verification.
Illustrative walkthrough: these examples do not create requests, run an agent, or record approvals. Open a real sample to explore the review workspace.
A reply, a completed agent task, and an approval answer different questions. None silently substitutes for the others.
Each checkpoint answers a different question and leaves the final preference or approval decision with a person.
Inspect repository and environmental evidence, then classify feedback as blocker, material risk, suggestion, question, or positive observation.
Choose CLI for a local file-backed review or MCP for an existing remote/provider-backed review. Combine them only for distinct operations.
Inspect thread authorship and gate state. Reply or revise when appropriate; do not resolve independently authored feedback prematurely.
The agent can report that evidence and acceptance criteria are satisfied. Only the existing human-controlled path approves downstream work.
Six illustrative stages show how a bounded Inbox request becomes a careful review when the decision needs evidence.
The request names the sender, the launch decision, and the artifact to inspect. Reading it alone does not complete the task.
Open the launch brief in Preview. Use Document or Changes independently from Preview or Raw.
Attach the rollback-owner question to the affected section so the next revision has precise context.
A connected agent retrieves scoped feedback and revises the source. Its completion report remains a claim about work performed.
Read the exact comparison and check the rollback evidence. Resolving a conversation does not establish human sign-off.
An authorized reviewer accepts or requests changes for the exact revision. Approval does not automatically merge, deploy, or verify external execution.
Start with the sample, then install the review pack when you are ready to connect a local file or remote review.