creating-pull-requestslisted

# Creating Pull Requests Open GitHub pull requests with `gh` in the author's style. Write like the author already writes. Stay brief. Skip fluff. ## Goal Create a PR that is ready for review, uses the correct repo and base branch, reflects the author's writing style, and includes only the context reviewers actually need. ## Use This Skill When - The user asks to create, open, publish, or send a PR or pull request - The user asks for a draft PR or signals the work is not ready to merge - The branch is done and opening a PR is the next obvious step ## Non-Negotiables - Use `gh` for GitHub operations - Be concise and direct - Do not use emojis - Do not open a PR until the branch is pushed and relevant local checks are done or a clear blocker is reported - Do not depend on `gh pr create --fill` unless the repo template makes that the cleanest option - Return the PR URL after creation - When no repo template exists, prefer a problem-first PR body: problem, rationale, user impact, evidence, and focused visual/demo proof when useful ## Core Workflow 1. Inspect branch state and confirm there is real work to propose. 2. Check whether a PR already exists for the current branch. Do not create duplicates. 3. Infer the target repo, remote, and base branch automatically. 4. Look for a repo-provided PR template. Use it when present. 5. Inspect the last 5-7 PRs and issues authored by the user and mirror the style. 6. Identify and run the most relevant local quality checks for this r