gwt-prlisted

Create or update GitHub Pull Requests with the gh CLI, including deciding whether to create a new PR or only push based on existing PR merge status. Use when the user asks to open/create/edit a PR, generate a PR body/template, or says 'open a PR/create a PR/gh pr'. Defaults: base=develop, head=current branch (same-branch only; never create/switch branches).
akiojin/llmlb · ★ 6 · Code & Development · score 71

Install: claude install-skill akiojin/llmlb

# GH PR ## Overview Create or update GitHub Pull Requests with the gh CLI using a detailed body template and strict same-branch rules. ## Decision rules (must follow) 1. **Do not create or switch branches.** Always use the current branch as the PR head. 2. **Only `develop` may target `main`.** If the base is `main` and the head branch is anything other than `develop`, **refuse to create the PR** and instruct the user to merge into `develop` first, then create a release PR from `develop`. 3. **Check local working tree state before push/PR operations.** - `git status --porcelain` - If output is non-empty (tracked or untracked changes), pause and ask the user what to do. - Present 3 options: continue as-is, abort, or manual cleanup then rerun. - **Do not** run `git stash`, `git commit`, or `git clean` automatically unless explicitly requested. 4. **Check for an existing PR for the current head branch.** - `gh pr list --head <head> --state all --json number,state,mergedAt,updatedAt,url,title,mergeCommit` 5. **If no PR exists** → create a new PR. 6. **If any PR exists and is NOT merged** (`mergedAt` is null) → push only and finish (do **not** create a new PR). - This applies to OPEN or CLOSED (unmerged) PRs. - Only update title/body/labels if the user explicitly requests changes. 7. **If all PRs for the head are merged** → check for post-merge commits (see below). 8. **If multiple PRs exist for the head** → use the most recently updated PR for reporting, b