@mattpocockuk: Thinking about creating a /pr skill. You invoke it to create a PR that: - Makes human review as fast and as simple as p…
Summary
A tweet discussing the idea of creating a /pr skill to improve pull request creation in AI tools, addressing issues with current PR body generation and suggesting features like risk assessment and evidence display.
View Cached Full Text
Cached at: 09/17/26, 10:24 AM
Thinking about creating a /pr skill. You invoke it to create a PR that:
- Makes human review as fast and as simple as possible
- Takes the best parts of /show-me by @dexhorthy
- Uses your domain language (from /grill-with-docs)
- Shows evidence that the change works (images, test output etc)
- Assesses merge risk (is it a one-way door, or a two-way door?)
IMO every model/harness I’ve seen creates garbage PR bodies - needs a skill here.
WDYT?
Similar Articles
@mattpocockuk: mattpocock/skills v1.3 is out! - /pr (new) writes easy-to-read PR bodies, showing hard evidence that the changes work a…
Matt Pocock released v1.3 of his mattpocock/skills package, adding new Claude Code skills: /pr for writing evidence-based PR bodies with merge risk assessment, /implement-spec for implementing specs and tickets via subagents, and /retro for reviewing coding agent sessions and suggesting repo improvements, plus renaming CONTEXT.md to GLOSSARY.md.
@mattpocockuk: Submitted a session to @aiDotEngineer Paris "Fixing The PR Bottleneck" - all about how you can apply software fundament…
A tweet announces that a session titled 'Fixing The PR Bottleneck' has been submitted to the AI Engineer Paris event, focusing on applying software fundamentals and automated review to speed up pull requests, with the session to be recorded and shared on YouTube.
@mattpocockuk: Thinking about making a skill called /fix-one-thing: "Read CODING_STANDARDS.md. Find a violation in the codebase, and f…
A tweet proposing the creation of an automated skill called /fix-one-thing to read coding standards and fix violations in the codebase.
@mattpocockuk: Prompt of the day: /retro take a look at as many GitHub PR review comments as you have access to from my team. Create s…
Matt Pocock shares a daily prompt idea: retroactively analyze GitHub PR review comments from a team and generate suggestions for updating CODING_STANDARDS.md, turning past code review feedback into forward-looking coding guidelines.
@mattpocockuk: One thing missing from my skill set is what compound engineering has - the promise that your process improves over time…
A tweet explores the gap in AI skills for process improvement over time, suggesting a potential tool like '/improve-me' to update coding standards and refine agent behaviors.