PR gives the model the shape of a pull request body: Summary, Evidence and Merge Danger. It tells the model to skip preambles, keep prose brief and use the project’s language from GLOSSARY.md.
The skill’s metadata credits the show-me skill by Dex Horthy of Humanlayer.
What You Get
- A Markdown template with three sections
- Worked examples of each summary visual, including diff sketches for component, file layout, call tree and control flow changes
- A ranking of evidence: screenshots are S-tier for visual changes and execution output such as test results is A-tier
- A one-way or two-way door call and a one-word blast radius
Common Use Cases
- Writing the body of a pull request an agent opens
- Showing reviewers a file-layout change as a diff of a tree
- Flagging a destructive or hard-to-reverse change before merge
What Makes It Unique
Its summary section is a diagram or sketch chosen to fit the change, and the guidance says to use one visual or several with judgement. Evidence is graded by tier, and the merge section frames risk as reversibility.
Under The Hood
A single SKILL.md of Markdown instructions with a template and examples. It runs no scripts and reaches no network. The model applies it when it writes a PR body, and reads GLOSSARY.md for domain wording when the file exists.