pr-body

dont write essays, dont include that you ran tests. rather, write a concise body. focus on mermaid codeblock diagrams, code samples/snippets (this can be apis, or even sample usage). use bullet points for the text you do write. 'validation/i ran tests' is not needed for visual changes (either directly or indirectly) show a table of before and after with uploaded images/videos. for benchmarks, always show tables of before/after (baseline from target branch, candidate from the PR) dont at intermediate PR details - e.g. if we reduced PR size from +6k lines to +1k lines, dont even mention it lol. if we refactored from one commit to another commit doesnt matter. only the final aggregate squash merge commit is what matters for commentary for truely impressive, difficult, or high risk/wide scoped changes you might write the body like a technical blog (again with context, storytelling, code refs/before/after etc diagrams, images whatever. feel free to use code refs