pr-describe

# /pr-describe — make the PR readable before the diff Generate a title and description that let a reviewer grasp **what changes** without opening the diff. Optimise for being understood, not for being exhaustive. **This skill never modifies files in the repository.** It edits the PR on GitHub, and writes its draft body to a temporary file outside the repo. ## Preconditions | Condition | If unmet | |---|---| | `gh` is authenticated and a PR exists for this branch | Stop and report it. Do not create a PR unasked. | | The working directory is the repository that owns the target PR | Stop. See the cross-repository hazard below. | ## Position in the workflow | Upstream | This skill | Downstream | |---|---|---| | implementation done, PR opened | `/pr-describe` | request review | ## Files to read ### Always read | File | Why | |---|---| | `${CLAUDE_SKILL_DIR}/reference/pr-template.md` | The body template and the writing rules. | ### Read only if | File | Trigger condition | |---|---| | the `artifact-design` skill | Only when publishing the visual summary, and only if the Artifact tool exists in this environment | --- ## Steps ### Step 1. Identify the PR — and confirm it is the right one ```bash gh pr view --json number,title,baseRefName,headRefName,url ``` **`gh` runs against the repository in the current working directory.** `gh pr edit <number>` from the wrong directory edits *that* repository's PR with the same number — an unrelated PR. Before editing anything, st...