pr-summary

Generate pull-request titles and descriptions from branch commits for reviewer-oriented prose.

Updated Aug 16, 2026
One-click install
npx skills add https://github.com/Hallmanac/hall9k --skill pr-summary-hallmanac
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-summary
Source: https://github.com/Hallmanac/hall9k/tree/main/.claude/skills/pr-summary
Command: npx skills add https://github.com/Hallmanac/hall9k --skill pr-summary-hallmanac

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about pr-summary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a pull request description from branch commits?

Gather commits with git log origin/main..HEAD, inspect the diff with git diff --stat, then write prose grouped by reviewer concern rather than commit order. This Skill automates that process and outputs a title plus body in a fenced block.

How does the Hall9k PR SUMMARY block work?

A build session writes the title and body under a line reading exactly PR SUMMARY: in its final message. The Hall9k daemon reads that block and places it verbatim into the pull request it opens, adding the work-item line, acceptance criteria, and footer itself.

Can this skill open or edit a pull request directly?

No. The skill outputs text only and never runs gh pr create or gh pr edit. The Hall9k daemon opens PRs, and replacement bodies for already-open PRs are handed back for a human to apply.

What happens if the repository has its own PR description convention?

The repository's own PR-description rule wins for the prose. The skill adopts that rule's voice, section shape, and title convention, and only supplies what the repo's rule does not cover.

How are linked Jira or GitHub work items handled in the PR body?

The skill reads the external-reference line from task.md frontmatter, resolving jira:KEY to a browse URL and github:owner/repo#number to an issue URL. In a build session's PR SUMMARY block the line is omitted because the daemon adds it.