update-pr

# Update PR Title and Description Read the current PR title and body, analyze what changed in the session, and draft an updated title and description that preserves the original writing style. ## Step 1: Fetch Current PR Fetch the current PR details: ```bash gh pr view [PR_NUMBER] --json number,title,body,baseRefName,headRefName,updatedAt,commits ``` Omit PR_NUMBER to auto-detect from current branch. ## Step 2: Analyze the Existing Style Before drafting, study the current title and body to identify: - **Title format** — length, prefix conventions (e.g., `feat:`, `fix:`), capitalization - **Body structure** — headings, bullet points, sections, line length - **Tone** — formal vs. casual, terse vs. detailed - **Content patterns** — does it explain the "why", list changes, include test plans? - **Diagrams** — does the body contain Mermaid code blocks (sequence, state, or other)? ## Step 3: Evaluate Whether an Update Is Needed Use the PR's `updatedAt` field and commit timestamps to determine whether new commits were added since the body was last edited. If `commits_since_body_change` is empty, the description is already up to date — say so and stop. If there are commits since the last body change, check the incremental diff to assess significance: ```bash git diff origin/<base>...HEAD --diff-filter=d --stat -- $(git diff --name-only --since="<body_last_changed>" origin/<base>..HEAD) ``` Skip the update if the incremental changes are trivial (formatting, typos, config...