# Hide your slop PR descriptions behind

DevFeed: [Hide your slop PR descriptions behind](<https://devfeed.tech/articles/hide-your-slop-pr-descriptions-behind-122822.md>)

Original publisher: [Read original article](<https://simonwillison.net/2026/Nov/9/details-summary/>)

Author: Simon Willison

Published: 2026-11-09T04:25:05Z

Content type: opinion

Language: en

Sources: [Simon Willison](<https://devfeed.tech/sources/simon-willison.md>), [Simon Willison's Weblog](<https://devfeed.tech/sources/simon-willison-s-weblog.md>)

Topics: [ai slop pull requests](<https://devfeed.tech/topics/ai-slop-pull-requests.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [codex](<https://devfeed.tech/topics/codex.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [Image](<https://devfeed.tech/topics/image.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-2-312](<https://devfeed.tech/tags/ai-2-312.md>), [ai-assisted-programming](<https://devfeed.tech/tags/ai-assisted-programming.md>), [ai-assisted-programming-408](<https://devfeed.tech/tags/ai-assisted-programming-408.md>), [ai-writing](<https://devfeed.tech/tags/ai-writing.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [claude-opus](<https://devfeed.tech/tags/claude-opus.md>), [claude-opus-5-5](<https://devfeed.tech/tags/claude-opus-5-5.md>), [codex](<https://devfeed.tech/tags/codex.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [coding-agents-265](<https://devfeed.tech/tags/coding-agents-265.md>), [commits](<https://devfeed.tech/tags/commits.md>), [datasette](<https://devfeed.tech/tags/datasette.md>), [datasette-1-557](<https://devfeed.tech/tags/datasette-1-557.md>), [details](<https://devfeed.tech/tags/details.md>), [editorial](<https://devfeed.tech/tags/editorial.md>), [effort](<https://devfeed.tech/tags/effort.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [generative-ai-2-051](<https://devfeed.tech/tags/generative-ai-2-051.md>), [github](<https://devfeed.tech/tags/github.md>), [github-199](<https://devfeed.tech/tags/github-199.md>), [html](<https://devfeed.tech/tags/html.md>), [html-101](<https://devfeed.tech/tags/html-101.md>), [llm](<https://devfeed.tech/tags/llm.md>), [llm-647](<https://devfeed.tech/tags/llm-647.md>), [llms](<https://devfeed.tech/tags/llms.md>), [llms-2-015](<https://devfeed.tech/tags/llms-2-015.md>), [markdown](<https://devfeed.tech/tags/markdown.md>), [markdown-36](<https://devfeed.tech/tags/markdown-36.md>), [pr](<https://devfeed.tech/tags/pr.md>), [slop](<https://devfeed.tech/tags/slop.md>)

## AI overview

The author's approach to lengthy AI-written pull request descriptions is to lead with a short, human-curated explanation, optionally add a screenshot, and place the full agent-written description inside GitHub-supported `<details><summary>` tags. The summary line can identify the model and effort level, leaving readers free to expand the detailed account. The author says this keeps the information available while making the PR easier to scan; the opener may be written by a person or selected from text the agent produced.

## Source excerpt

Most of the changes I make to my projects these days come in the form of PRs opened for me by Claude Code or Codex. The PR is my unit of work - I use them to bundle commits together, iterating on them until a feature is complete, document decisions and then merge the finished result. Today's coding agents are great at writing PR descriptions. They're too good at describing the work The problem is that they are too good. An agent-written PR description is accurate and comprehensive. It describes the problem, the detailed solution, and the steps taken to verify it. That's a lot of information to absorb. It's not necessarily slop, but it reads like slop! It's very easy to spot an AI-written PR, and as with other forms of AI writing my instant reaction is best summarized as "I'm not reading all of that". It doesn't matter how accurate or useful the information is, I'm instantly put off by the thought that it will take me longer to read than it took the driving author to write... even when that driving author is me! I want human editorial judgement. I want someone to have thought just long enough about the PR to give me a human-approved introduction that helps me understand, at a high level, what the PR is for and whether it deserves more of my attention. I think I've found a low-effort way to do this that feels right. Hide most of it in a details/summary The HTML <details><summary> elements render as a collapsed heading (the summary) that can be expanded to view the larger piece of text. The code looks like this: <details> <summary>Claude Opus 5.5</summary> <h2>The hook</h2> Plugins implement <code>register_agent_reference_types(datasette)</code>... </details> When rendered, it looks like this: Crucially, <details><summary> is supported in GitHub Markdown. You can drop those tags directly into an issue comment or PR description and GitHub will hide the details and display just the summary plus an expansion arrow. I've started using this for my AI-generated pull requests