update-pr-description

Source excerpt starting at line 1.

1---2name: update-pr-description3description: Evaluate a PR's title and description against its actual implementation, then iteratively suggest and apply updates. Use when the user asks to check, fix, or update a PR title or description.4---5 6# Update PR Description7 8## Workflow9 101. **Resolve the PR.** Use the number/URL the user provided. If none, look up the PR for the current branch with `gh pr view`.112. **Gather evidence:**12   - `gh pr view <pr> --json title,body`13   - `gh pr view <pr> --json commits` (commit messages)14   - `gh pr diff <pr>` (full diff against base)153. **Evaluate divergence.** Compare the stated title/description against what the commits and diff actually do. Only flag *meaningful* divergence (wrong scope, missing major changes, stale claims, inaccurate summary). Ignore trivial wording.164. **Report.** Tell the user whether the title and/or description meaningfully diverges. If not, stop here.175. **Suggest iteratively.** Propose concrete updated title/description. Ask the user one change at a time whether to apply, accept edits, and refine.186. **Apply.** Once agreed, update on the user's behalf with `gh pr edit <pr> --title ... --body ...`.19 20## Notes21 22- Match the repository's existing PR template/style if the body uses one.23- Don't rewrite a description that's already accurate.24- Update the state of checkboxes where appropriate.25- Remove section placeholders/reminders when filling out a section.26- Do not remove the canary release section.