Menu
Generate a PR summary from all commits since the branch diverged from a given parent branch, written to pr-summary.msg
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | pr-summary |
| description | Generate a PR summary from all commits since the branch diverged from a given parent branch, written to pr-summary.msg |
| allowed-tools | Bash, Read, Grep, Glob |
Analyze all commits on the current branch since it diverged from the parent branch and write a summary to pr-summary.msg.
Arguments: $ARGUMENTS — the parent/base branch to diff against (e.g. main, dev, master). This argument is required.
If $ARGUMENTS is empty, ask the user to provide the parent branch (e.g. /pr-summary main). Do not assume a default.
Ensure pr-summary.msg is in the .gitignore in root of repo:
if [ ! -f .gitignore ] || ! grep -qF "pr-summary.msg" .gitignore; then
echo "pr-summary.msg" >> .gitignore
fi
Find where the current branch forked from the provided parent branch:
BASE=$(git merge-base HEAD $ARGUMENTS)
git log --reverse --pretty=format:"%h %s%n%b" $BASE..HEAD
Also run git diff $BASE..HEAD --stat to get a file-level change summary.
Read key changed files to understand what the commits actually do. Use git diff $BASE..HEAD for the full diff if needed, but focus on understanding the intent, not reciting code.
pr-summary.msgDelete any existing pr-summary.msg first. Write the summary with this structure:
## Problems to Solve
<Describe the problems this PR addresses, based on commit messages and changed files. Focus on the "why" and "what", not the "how".>
## Summary
<1-3 bullet points describing the high-level purpose of this branch>
## Changes
<Bulleted list of specific changes, grouped logically>
## Test plan
<How to verify these changes work — mention relevant test commands, manual steps, or areas to check>
Keep it concise. Focus on why and what, not how. Group related commits into logical changes rather than listing every commit verbatim.
After writing the summary, open a pull request on GitHub or your git hosting provider.
Use the contents of pr-summary.msg as the PR description to provide reviewers with context and an overview of the changes.
Create the PR with gh CLI tool.
For example, if the current branch is feature-branch and the parent branch is main, you can run:
gh pr create --base main --head feature-branch --title "PR Summary" --body-file pr-summary.msg
Create a GitHub issue from a summary description. Drafts the title and body, shows a preview, and asks for confirmation before publishing.
Thorough peer code review of a PR or branch — correctness, bugs, logic errors, edge cases, code quality, simplicity, naming, test coverage. Takes a PR number or base branch argument. Pulls PR metadata via gh if available.
Autonomous Quint formal specification workflow — generate specs (new or from codebase), typecheck, create witnesses, run invariants, and verify. Like plan mode but for formal specs.
Merge a branch into the current branch — detect conflicts, summarize them, and resolve them automatically where possible. Asks the user when unsure which changes to keep.
Write a commit message following the project template and save it to commit.msg
Verify documentation (README, runbooks, module docs) aligns with the actual codebase and fix any drift