Put a reviewed introduction before an agent’s long PR description
Simon Willison puts a short, human-reviewed introduction at the top of an agent-written pull request and collapses the longer explanation inside GitHub’s details and summary tags. The opening tells reviewers what changed and why it deserves attention; implementation notes and verification remain available below. The technique preserves useful evidence while asking the author to decide which information matters first.
Simon Willison · Nov 9, 2026
Why it matters
Reviewers benefit from a clear entry point even when an agent can produce an accurate description of every implementation detail.
More context
Try the pattern on one PR: write or select the smallest accurate problem-and-result explanation, add a screenshot when it helps, and place secondary detail underneath. Willison labels the collapsed section with the model and effort level; that is his practice rather than a required convention.
Keep in mind
This is an author’s communication preference, not a measured review-speed improvement. Critical risks, migration steps and unresolved failures should remain visible rather than hidden in the collapsed section.
Original read