gh-prlisted

# Skill: gh-pr ## Purpose Open a well-written PR for the current branch: a faithful summary of the changes, links to the issue and spec, and a verifiable test plan. ## Preconditions (check, fix if needed) 1. Current branch ≠ default branch. Otherwise, offer to create one (`feat/<ref>-<slug>` or `fix/<slug>`). 2. Everything is committed and pushed (`git status`, `git push -u origin HEAD`). The flux-gate hook runs the gates on push: if it blocks, fix the failures first, never bypass it. 3. Read `flux-config.yml`: `github.labels` = default PR labels. ## Writing - **Title**: conventional commit format (`feat(candidates): add pipeline board`); it often becomes the squash-merge commit message. - **Body**: build it from the actual diff (`git diff main...HEAD`), not from memory: ```markdown ## Summary [What the PR does and why, 2-4 sentences] Closes #N <!-- if an issue is linked; otherwise omit --> Spec: `specs/SPEC-<ref>.md` <!-- if applicable --> ## Changes - [Notable change, grouped by intent] ## Test plan - [Command or manual step to verify, with expected result] ## Review notes - [Debatable tradeoff, accepted debt, area worth a close look] ``` - Only list what helps the reviewer: no file-by-file inventory, the diff already shows that. ## Creation and follow-up 1. `gh pr create --base main --title "…" --body "…" --label <labels>`. 2. Give the URL to the requester and restate the circuit: green CI, then a review on request (`/flux:revie