Skip to content
important Productivity

Simon Willison proposes hiding AI-written pull request descriptions in a collapsible HTML element

only one source so far

Simon Willison recommends hiding detailed AI-generated pull request descriptions behind a details/summary HTML element and putting only a short human summary at the top, so PRs don't come across as low-quality AI text.

Simon Willison, author of the Datasette tool and a commentator on the LLM scene, described on his blog the approach he uses for pull requests generated by agents like Claude Code or Codex. According to him, PR descriptions written by these agents are accurate and complete in content, but their length and style come across as low-quality AI text ("slop") – the reader is put off by the length, even though the information itself is useful.

According to Willison, the solution is to place a short, human-written summary at the top of the PR explaining the essence of the change, possibly supplemented with a screenshot, and hide the entire detailed text generated by the agent inside a details/summary HTML element, which GitHub supports in Markdown. The result is a collapsible section: the reader sees only a brief summary with an arrow to expand it, while the details remain available with a click. As the text in the summary, he uses the model name and the reasoning level (effort), for example "Claude Opus 5.5 Medium," to make it clear that the text was generated by AI.

In the article, Willison also offers a practical aid for remembering the tag order – he recommends thinking of them as a joined word, "details-summary," where details wraps the entire content and summary is the clickable title.

What changed

Why it matters

For code reviewers, this means less time spent reading lengthy AI-generated texts in PRs and faster orientation thanks to a human-verified summary. For teams working with AI coding agents, it is a simple, free workflow tweak that requires no change of tools – standard Markdown support on GitHub is enough.

Two audiences, two different impacts

What this means

01

For individuals

Developers working with tools like Claude Code or Codex can immediately adjust the way they write pull request descriptions to keep them readable and clear.

What to do When writing PRs with the help of AI agents, add a short custom summary at the top and hide the detailed AI-generated text inside a details/summary HTML element.
More practical updates →
02

For a business

Teams using AI coding agents can use this approach to speed up code review and reduce reviewer fatigue from lengthy AI-generated PR descriptions, if they adopt such a convention themselves.

Development
What to decide Consider introducing a convention of hiding AI-generated pull request descriptions behind a collapsible HTML element as a standard for code review in the team.
More business impacts →
AI agents Claude Code Codex GitHub PR description

Check the original

Event sources

only one source so far · 1 publisher, 1 independent. We count feeds from the same owner only once.

1
Simon Willison — AI tag (leading independent LLM commentator) community signal · first detected Hide your slop PR descriptions behind <details><summary>