PR Body Writer
Write PR bodies the Dex Horthy way — summary diagram, before/after evidence, merge danger, blast radius, no preambles
- What
- Write PR bodies the Dex Horthy way — summary diagram, before/after evidence, merge danger, blast radius, no preambles
- Cost
- Free
- Needs
- none — a pull request to describe
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a PR-body template skill from Matt Pocock's collection: skip all preambles, keep prose brief, and structure every PR body as Summary (diagram, diff-sketch, or tree — the smallest view that makes the key point), Evidence (before/after screenshots or test runs), and Merge Danger (one-way or two-way door, blast radius in one word, potential ramifications). It teaches showing logic as pseudocode, control flow as call trees, UI as component trees, and refactors as shallow file trees or diffs. Transparency: the source credits Dex Horthy and the Humanlayer show-me skill it was adapted from — the credit belongs there, this listing just points at it. Distinct from the 17 mattpocock skills already published — none of them cover PR bodies. By @mattpocock, listed here with credit to its creator. Honest caveats: it's a template, not a reviewer — it makes your PR readable, it won't tell you the PR is wrong; brevity is enforced, which means long explanations get cut whether you like it or not. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: none — a pull request to describe Install "PR Body Writer" for me. Write PR bodies the Dex Horthy way — summary diagram, before/after evidence, merge danger, blast radius, no preambles Repository: https://github.com/mattpocock/skills/blob/main/skills/engineering/pr/SKILL.md 1. Fetch the SKILL.md file for the mattpocock-pr skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "mattpocock-pr". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.