What problem does it solve? Writing a pull-request description that actually helps a reviewer is hard: commit-ordered changelogs, restated diffs, and agent run transcripts tell a reviewer nothing. This Skill turns the commits on a branch into a title and body organized around what a reviewer needs to think about, with the why placed next to the change it explains. ## Core Features & Use Cases - PR SUMMARY block for Hall9k build sessions: Produces the closing PR SUMMARY: block that the Hall9k daemon places verbatim into the pull request it opens, leaving out the work-item line, acceptance criteria, and footer the platform adds itself. - Replacing an open PR's body: Reads the current body with gh pr view, preserves carried-forward residual notes and the run/token footer, and drafts a replacement for a human to apply. - House-style awareness: Defers to a repository's own PR-description rule and an owner's configured voice skill, and follows project writing conventions such as the no-em-dash rule. - Use Case: A build session finishing a Hall9k task gathers git log and git diff against origin/main, resolves the linked Jira or GitHub work item, and emits a title plus grouped, reviewer-oriented prose under a PR SUMMARY: line. ## Quick Start Ask the agent to generate a PR title and description from the commits on the current branch versus origin/main, formatted as a PR SUMMARY block.