--- title: The /show-me skill that makes PR reviews actually readable description: A new Cursor skill called /show-me generates diagrams and visual summaries directly inside PR descriptions, aiming to fix the common problem of vague,... canonical: https://daily.dev/posts/the-show-me-skill-that-makes-pr-reviews-actually-readable-uxxbb7vsn twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: The /show-me skill that makes PR reviews actually readable | daily.dev og:description: A new Cursor skill called /show-me generates diagrams and visual summaries directly inside PR descriptions, aiming to fix the common problem of vague,... og:url: https://daily.dev/posts/the-show-me-skill-that-makes-pr-reviews-actually-readable-uxxbb7vsn og:image: https://api.daily.dev/og/posts/uxxbB7vsn.png og:image:alt: The /show-me skill that makes PR reviews actually readable og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # The /show-me skill that makes PR reviews actually readable **[Trends](https://daily.dev/sources/trends)** · 1 min read · 2 upvotes · 0 comments ## Summary A new Cursor skill called /show-me generates diagrams and visual summaries directly inside PR descriptions, aiming to fix the common problem of vague, hard-to-review pull requests. Built by dexhorthy and praised by mattpocockuk as 'a toolbox of nice ways to look at code,' it's gaining traction because it slots into existing review workflows rather than requiring a new tool. Reaction so far is enthusiastic but early, and the real test will be whether it holds up on messy, multi-concern PRs rather than clean demo diffs. ## Content AI-generated PRs have a readability problem. The code might be fine, but the descriptions are often walls of text that nobody wants to parse. Matt Pocock's take: `/show-me` by @dexhorthy is the fix. The skill plugs into your PR workflow and gives you a toolbox of visual ways to look at code changes. Think diagrams, structured breakdowns, things that make a diff actually scannable. Pocock called it "phenomenal" for making AI-authored PR descriptions easy to read, and the retweets suggest he's not alone in that frustration. Qodo AI chimed in with the same angle: diagrams help. Which sounds obvious until you realize almost nobody is doing it by default. The broader question Pocock floated - what techniques are people actually using to make AI-authored PRs reviewable - hasn't gotten a definitive answer yet. `/show-me` is one answer. The fact that it's getting this much traction suggests the problem is real and the tooling is still catching up. ## Questions this post answers ### What is the /show-me Cursor skill and what does it do? It is a Cursor skill built by dexhorthy that automatically generates diagrams and visual summaries inside pull request descriptions so reviewers can see what changed instead of inferring it from a diff. It has been praised by developers like mattpocockuk as 'a toolbox of nice ways to look at code,' and is gaining attention in the TypeScript community for making PR review easier without requiring a separate tool or workflow change. _Developers evaluating new PR review tooling can follow early reactions and comparisons on daily.dev._ ## Community take How the wider developer community reacted, aggregated from 2 discussions and 77 comments across x (as of 2026-09-13). **TL;DR:** Reaction is largely enthusiastic and practical — developers are already integrating /show-me into their workflows alongside other skills like grill-me and plannotator, though a few flag friction with skill discovery, invocation, and tooling limitations. **Sentiment:** 68% positive · 24% mixed · 8% skeptical **The case for** - Several people say they've already adopted it into daily workflows for PR bodies and bug/feature explanations. - It's praised as composable because it's framed as a reusable skill file rather than a one-off prompt. - Some see it saving review time by letting reviewers grasp structure visually instead of parsing a wall of text first. **The pushback** - One person notes it isn't explicitly invoked, requiring a fork-patch, and points to broader 'skill hell' where too many skill descriptions get compressed on startup. - Another flags that CLI tools don't render mermaid diagrams well. - A couple of replies push back that readability tooling only solves half the problem since someone still has to actually review the changed code path. **By community** - x (positive): Replies show quick, genuine adoption chatter with people sharing complementary skills and workflows, alongside scattered technical caveats and off-topic noise. **Open questions** - How well does the skill hold up on messy, multi-concern PRs versus clean demo diffs? - Does it work well across different editors/environments like VS Code, given mixed signals on tool support? **Highlights** > @mattpocockuk @dexhorthy It is not explicitly invoked though, so I will have to fork-patch to use :( Skill hell is causing codex and others to complain that skill descriptions are getting compressed on startup because there are too many of them. Most don't need to be implicitly invoked. > — [sandipb on x](https://x.com/sandipb/status/2095501405339402657) > @mattpocockuk @dexhorthy Its great, unfortunately the cli tools are not good at showing mermaid graphs > — [KarifYuval on x](https://x.com/KarifYuval/status/2095463036110749783) > @mattpocockuk @dexhorthy I've been using it to generate my PR bodies since I found it, great skill > — [MarstonConnell on x · 1 points](https://x.com/MarstonConnell/status/2095485128218730630) > @mattpocockuk @dexhorthy skills like this work best when the skill file is the plan, not a prompt wrapper — one md the agent re-reads per pr keeps the review shape stable across sessions. what breaks it is stuffing repo context into the same window instead of pointing at diffs. > — [inc\_ongi on x](https://x.com/inc_ongi/status/2095472495423865276) > @mattpocockuk @dexhorthy Readable PR descriptions are half the review battle. The other half is a reviewer who didn't write it actually clicking through the changed path. > — [MatinMatano on x](https://x.com/MatinMatano/status/2095474265034539219) **Source threads** - [x](https://x.com/HamelHusain/status/2095517400217293247) · 0 points · 0 comments - [x](https://x.com/mattpocockuk/status/2095460192871698728) · 0 points · 77 comments ## Similar posts on daily.dev - [6 Best Practices for Human Reviewers: How to Review AI-Generated Code](https://daily.dev/posts/6-best-practices-for-human-reviewers-how-to-review-ai-generated-code-xuylblot0) · Aviator Blog · 0 upvotes · 0 comments - [Streamline Your Code Reviews: How AI-Powered PR Summaries Save Time and Improve Team Collaboration](https://daily.dev/posts/streamline-your-code-reviews-how-ai-powered-pr-summaries-save-time-and-improve-team-collaboration-bemzckiar) · Atomic Spin · 1 upvotes · 0 comments --- Tags: [#devtools](https://daily.dev/tags/devtools), [#code-review](https://daily.dev/tags/code-review) [View this post on daily.dev](https://daily.dev/posts/the-show-me-skill-that-makes-pr-reviews-actually-readable-uxxbb7vsn) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"The /show-me skill that makes PR reviews actually readable","url":"https://daily.dev/posts/the-show-me-skill-that-makes-pr-reviews-actually-readable-uxxbb7vsn","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/the-show-me-skill-that-makes-pr-reviews-actually-readable-uxxbb7vsn"},"datePublished":"2026-09-03T14:21:12.679Z","dateModified":"2026-09-13T19:55:34.679Z","description":"A new Cursor skill called /show-me generates diagrams and visual summaries directly inside PR descriptions, aiming to fix the common problem of vague,...","isAccessibleForFree":true,"articleSection":"Trends","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Trends","logo":"https://media.daily.dev/image/upload/s--ZfSp3asX--/f_auto,q_auto/v1780996004/logos/trends?_a=BAMAMiWQ0","url":"https://daily.dev/sources/trends"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/the-show-me-skill-that-makes-pr-reviews-actually-readable-uxxbb7vsn","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"devtools,code-review","timeRequired":"PT1M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Trends","item":"https://daily.dev/sources/trends"},{"@type":"ListItem","position":3,"name":"The /show-me skill that makes PR reviews actually readable"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/the-show-me-skill-that-makes-pr-reviews-actually-readable-uxxbb7vsn#faq","mainEntity":[{"@type":"Question","name":"What is the /show-me Cursor skill and what does it do?","acceptedAnswer":{"@type":"Answer","text":"It is a Cursor skill built by dexhorthy that automatically generates diagrams and visual summaries inside pull request descriptions so reviewers can see what changed instead of inferring it from a diff. It has been praised by developers like mattpocockuk as 'a toolbox of nice ways to look at code,' and is gaining attention in the TypeScript community for making PR review easier without requiring a separate tool or workflow change. Developers evaluating new PR review tooling can follow early reactions and comparisons on daily.dev."}}]} ```