pull-request-descriptionlisted

# Skill: pull-request-description Draft a consistent, compact PR/MR **title** and **body**, then create or update the PR/MR. Goal: a structured, compact write-up that — in the best case — always links the issue it builds on. ## IMPORTANT - GitHub → `gh` CLI. GitLab → `glab` CLI. Never call the forge APIs directly. - Write the title and body in **English**, even when the conversation is in another language. - **Repo conventions win.** Only fall back to the bundled defaults when the repo defines none. - Always show the full draft and confirm before creating or updating anything. - If a required CLI is missing, abort and ask the user to install it, then restart the skill. - When a `gh`/`glab` call fails, use AskUserQuestion to ask how to proceed (retry / stop / other). ## Instructions ### Step 1 — Gather the change - **Base branch**: default to the repo's default branch (`gh repo view --json defaultBranchRef` or `git remote show origin`) unless the user names another. - **Commits & diff**: ```bash git log --oneline <base>..HEAD git diff --stat <base>...HEAD ``` Read enough of the actual diff to describe *why* and *what* accurately. Never invent changes. - **Detect the forge**: inspect `git remote -v` — `github.com` → GitHub, `gitlab` → GitLab. ### Step 2 — Find the linked issue Best-case PRs link the issue they build on. Look, in order: 1. Branch name (e.g. `123-…`, `feature/PROJ-123`, `fix/#123`). 2. Commit messages / bodies (`#123`, `Closes #123`, `PROJ-12