Hide your slop PR descriptions behind <details><summary>

Coding agents such as Claude Code and Codex now produce pull-request descriptions that are accurate and thorough, covering the problem, implementation, and verification. But that abundance can make them feel like AI-generated “slop”: readers may be put off by long explanations before they can tell whether a change matters. The proposed fix is to separate a short, human-curated introduction from the agent’s full account, preserving useful detail without demanding that everyone read it upfront.

GitHub Markdown supports HTML’s <details> and <summary> tags, which display a clickable summary and keep the enclosed text collapsed. A PR can therefore open with a concise explanation of its purpose, perhaps accompanied by a screenshot, followed by the longer agent-written description hidden in the expandable section. Examples include explaining a redesigned table-row page, clearer pagination, conditional loading of a large JavaScript file, a new plugin hook, or command-line tools for managing API endpoints. The short opener may be written by a person or drawn from the agent’s description, but it signals that someone has judged what readers most need to know. The tags’ order is easy to remember as “details-summary”: summary names the clickable line, while details wraps the rest. A GitHub editor button could make the pattern easier to use, especially on mobile.