pr-summary

PR Summary

Generate a clear pull-request title and description from a branch's git history.

When to use

The user has committed work on a feature branch and wants a PR title + description before opening the PR. Not for summarizing a single commit (just read the commit) or an already-merged branch.

Instructions

1. Gather the branch's context. Run the bundled helper, which prints the branch name, base branch, commit log, and changed-files summary:

   bash scripts/collect-context.sh
   

   If the helper can't run, gather the same data manually: git branch --show-current, the merge base against the default branch, git log <base>..HEAD, and git diff --stat <base>..HEAD.

2. Read the output and identify: the main change, why it was made, and any notable secondary changes (refactors, migrations, test additions).

3. Write the PR following the structure and rules in references/pr-style.md. Read that file now — it defines the title format, the section template, and what to leave out.

4. Present the result to the user as a single markdown block they can copy. Do not open or push the PR unless they explicitly ask.

Output

A PR title (one line) followed by a description with Summary, Changes, and Testing sections, ready to paste into the PR form.

References

• references/pr-style.md — title format, section template, and style rules. Read in step 3.