The scenario
The reviewer has not seen this conversation. Some requested checks may not have run.
Required context: a selected repository matching this scenario, relevant task evidence, and access to its instructions and checks. Use redacted or synthetic data where appropriate.
Adapt the complete prompt
Edits stay in this browser tab. Saving bookmarks the original example; export your edited version to keep it elsewhere.
Why this is a strong example
It makes the summary independently understandable while preventing confident prose from substituting for proof.
A concrete outcome
Write a concise completion summary from the current diff and actual verification evidence.
The result can be assessed against an observable task rather than prompt length or confidence.
Boundaries and a method
Inspect the intended change set and available output. Describe the problem, resulting behavior, scope and limitations. Do not invent successful checks or claim deployment from a local build.
This leaves implementation judgment while constraining the changes that would exceed the task.
Evidence that can disagree
Tie each verification claim to the relevant command/output or observation, and explicitly identify missing evidence.
These checks describe what would make acceptance justified; asking for them does not mean they ran.
A safe way to encounter uncertainty
If the repository contradicts these assumptions, required access is unavailable, or a consequential product decision is missing, explain the conflict and pause the dependent work. Preserve unrelated changes.
Consequential uncertainty stays visible rather than being converted into an invented requirement.