GitHub PR Create Skill

Process

1. Get the PR Description

• Check for .local/pr-body.md. If it exists, re-read it fresh and sanity-check that its content matches the current branch's changes (e.g. the description references files, features, or issues consistent with the current diff). If it looks stale or unrelated to the current changes, warn the user and offer to regenerate it.
• Else if the user already generated a PR description earlier in the conversation, use that.
• Otherwise, fall back to the pr-writer skill to generate the title and body.

2. Pre-flight Checks

Check for CONTRIBUTING.md (at the repo root or in docs/) and .github/PULL_REQUEST_TEMPLATE.md. Scan them for any recommended steps before opening a PR — common examples:

• Running a linter or formatter (e.g. npm run lint, cargo fmt)
• Running tests (e.g. npm test, pytest)
• Building the project
• Updating documentation or changelogs