github-pr-describelisted

# PR Description Generator Generate a structured PR description from the diff, then push it to GitHub. ## Phase 1 — Validate & gather If `$ARGUMENTS` is empty or not a number, ask via `AskUserQuestion`: *"Which PR number would you like me to describe?"* ```bash bash "${CLAUDE_SKILL_DIR}/scripts/gather-pr-info.sh" $ARGUMENTS ``` Returns `{repo, metadata, diff: {content, lines, bytes}}`. On `error`, stop. **Edge cases:** - `diff.lines == 0`: "This PR has no commits/changes yet. Nothing to describe." → stop. - `diff.lines > 5000`: delegate diff analysis to an `Agent` sub-call to avoid context bloat. Ask it to return a structured per-file summary of changes. - If `metadata.body` contains ticket links (`#123`, `JIRA-456`, issue-tracker URLs), preserve them for the final description. ## Phase 2 — Analyze the diff For every meaningful change (skip whitespace/format-only), extract: files changed, what (added/modified/removed), why, notable implementation details. Group related changes by area (UI, API, tests, config). ## Phase 3 — Draft Load `${CLAUDE_SKILL_DIR}/templates/description.md` and follow its section and formatting rules. Key points: - Only include sections that have relevant changes — omit empty sections. - TL;DR table + bullets always come first. - Preserve any ticket/issue links from the existing PR body under `**Tickets:**` at the top. - Concise but precise — a reviewer should understand the *what* and *why* without reading the code. - Never fabricate changes