github-pull-request

name	github-pull-request
description	Create or update a GitHub pull request with a structured What / Why / How / Test-plan body. Use when opening or updating a PR for the current branch.
metadata	{"author":"Médéric HURIER (Fmind)","source":"github.com/fmind/dotfiles/tree/main/skills/github-pull-request","created":"2026-06-23T00:00:00.000Z","updated":"2026-07-06T00:00:00.000Z"}

Create GitHub Pull Request

Create or update a GitHub pull request for the current branch against main.

Context Gathering

Gather context before drafting:

• git fetch origin main — refresh origin/main so the ranges below are accurate.
• git config --get remote.origin.url — origin URL.
• git branch --show-current — current branch.
• git status --short — working tree state.
• gh pr view --json number,state,url — detect an existing PR for this branch (exits non-zero / empty when none, keying the create-vs-edit choice).
• git log --reverse --oneline origin/main..HEAD — commits since main.
• git diff --stat --find-renames origin/main...HEAD — diff stats.
• git diff --name-only --find-renames origin/main...HEAD — changed files.

Workflow

1. If the current branch is main, stop and say a PR must come from a feature branch.

2. Inspect changed files as needed so the PR matches the actual work, not just the commit subjects.

3. Write a clear PR title in imperative mood, under 72 characters.

4. Write a Markdown body with these sections:

   ## What
   
   ## Why
   
   ## How
   
   ## Test plan
   

5. Push the current branch to origin with upstream if needed (git push -u origin <branch>).

6. If a PR already exists for this branch, update it:

   gh pr edit --base main --title "<title>" --body-file <tmpfile>
   

7. Otherwise create it:

   gh pr create --base main --title "<title>" --body-file <tmpfile>
   

8. Use a temporary file for the PR body instead of inline shell quoting.

9. After success, print the PR URL, the final title, and the final body.

10. If origin/main or GitHub auth is unavailable, explain the blocker briefly and stop.

Gotchas

• Keep the final response compact.
• Never force-push to main.

Documentation

• feature-branch — branch creation upstream of the PR.
• conventional-commit — commit cadence on the branch.