github-pull-requestlisted

# GitHub Pull Request Create or update a pull request for the intended branch and base, using the repository's template and a description proportional to the change. [feature-branch](../feature-branch/SKILL.md) owns branch creation; [git-add-commit-push](../git-add-commit-push/SKILL.md) owns commit and push repair. ## Workflow 1. **Resolve the target**: inspect `git status --short --branch`, the GitHub repository, and `gh pr view --json number,state,url,baseRefName,headRefName,headRefOid`. Distinguish no open PR from authentication or network failure. 1. **Choose the base**: use the user's explicit base, otherwise the existing PR's base, otherwise `gh repo view --json defaultBranchRef`. A PR needs different head and base branches; never assume every repository uses `main`. 1. **Read the actual change**: fetch the selected base, inspect its three-dot diff to `HEAD`, relevant source/tests, and the commits being proposed. Separate uncommitted work from the branch that GitHub will review. 1. **Draft the title and body**: use a short imperative title. Follow the repository PR template; otherwise use What, Why, How, and Test plan only where they add information. Explain the final behavior, reason, validation, and material limits. Write multiline content to a temporary file for `--body-file`. 1. **Check the outgoing artifacts**: scan the exact title and final body with `gitleaks stdin --redact` before publication, including edits made after drafting. Fail closed on scanner errors