Update PR Summary

SkillAI & models

This skill lets your AI rewrite a pull request's title and description based on all the changes in its branch. Once added, your AI can refresh a PR summary on request so the title and body stay accurate to the work that was done. It responds to requests like 'update PR summary', 'rewrite PR body', or 'refresh PR title and body'.

Available today. Use it from your connected AI after setup.

After adding the skill, go to the pull request you want improved and ask your AI to update the PR summary or rewrite the PR body. You can also ask for it by name using update-pr-summary.

Then ask your AI: use the Update PR Summary skill

What your AI can do with it

  • Rewrite a pull request title based on the changes in its branch
  • Rewrite a pull request description based on all changes in the branch
  • Refresh a PR's title and body when you ask it to
  • Update a PR summary so it reflects the full set of changes in the branch

What this skill tells your AI

The instructions your AI receives, as published by fcakyon/claude-codex-settings in plugins/github-dev/skills/update-pr-summary/SKILL.md and read by ahel’s review.

Update a PR title and description based on the complete changeset.

When explicitly invoked with extra text, treat that text as the PR number or URL.

Process

  1. Fetch PR info

    • Use gh pr view <pr> --json title,body,baseRefName,headRefName.
  2. Analyze the complete changeset

    • Use git diff <base-branch>...HEAD to review all committed changes in the branch.
    • Ignore unstaged changes.
    • Make the summary describe the full branch diff, not just the latest commit.
  3. Generate the updated summary

    • Follow the create-pr skill format for title and body.
    • Title: a short human headline, capital first letter, no fix: or feat: prefix. Lead with the outcome, punchy over exhaustive.
    • Body: open on why, then short scannable bullets (one point each). Lead with the most visual proof. A webpage, UI, or design change MUST carry before/after images in a two-column table, never text describing the change. See the create-pr skill for uploading them to a release.
    • Numbers win: put benchmarks, counts, speedups and comparisons in a markdown table.
    • One read, one section, no headers. Plain words, no buzzwords.
    • No test plans, file lists, or line links.
  4. Apply the update

    • Use gh pr edit <pr> --title "..." --body "...".

Signals

GitHub stars
1k
Forks
108
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
update-pr-summary
Source
github.com/fcakyon/claude-codex-settings