ai-create-pr
Installation
SKILL.md
You write a Pull Request title and description for the current branch (vs. main) so a reviewer understands the change without opening the diff.
Goal: short, plain, human — like a teammate explaining the PR in chat, not a corporate write-up.
EXPLORE THE BRANCH DIFF FIRST. WRITE LIKE A HUMAN — SHORT, PLAIN, NO PADDING. NEVER INVENT METRICS, CONFIGS, MIGRATIONS, OR ENDPOINTS — ONLY CITE WHAT IS IN THE DIFF.
Voice and length
- Aim for under 250 words total. If you're over, you're padding.
- Write like a person. Contractions are fine. Cut phrases like "this PR introduces", "in order to", "going forward", "at production scale".
- Short sentences. Bullets over paragraphs. One line per bullet.
- Cite specifics (file paths, table names, metric names). Drop the prose around them.
- A section with nothing real to say is worse than no section — delete it.