Awesome Pull Requests

Everyone knows that a good pull request has several characteristics:

• Small, focused changes
• Clear title and description
• Context (related issues, discussions)

But what makes it awesome is the “Accompanying gif” section.

A reduced PR template we used at Plan:

## 🌱 What does this PR do?

1. ...

## 📚 Storybook changes

1. ...

## 👆 Clickables

- ...

## 👏 Accompanying gif

Even if every other aspect of the PR is terrible, just try adding a gif to it ✨

Why /pr and /commit write to a file instead of passing inline arguments

Shell expansion corrupts inline messages. A PR body or commit message routinely contains !, backticks, $(), dollar variables, and glob characters. In zsh, ! triggers history expansion even inside single-quoted strings in certain contexts. Any of these can mangle the text before it reaches git or gh.

Both skills avoid this by writing the message to a file under /tmp/claude/ and pointing the command at it: git commit -F /tmp/claude/commit.txt and gh pr create --body-file /tmp/claude/pr.md. The message you composed is the message that lands.

The pattern generalises: whenever you generate text that feeds into a shell command and the command accepts a file argument, produce a file and point the command at it. The file is deleted after the command runs so the next invocation starts clean.