mcpbeat

Update Pr Summary

fcakyon/update-pr-summary

This skill should be used when user asks to "update PR summary", "update PR description", "rewrite PR body", "refresh PR title and body", or explicitly invokes "update-pr-summary".

384 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
955
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/fcakyon/claude-codex-settings --skill update-pr-summary

The instruction itself

2 sections, as written by the author

Update PR Summary

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

  • Fetch PR info
  • Use gh pr view <pr> --json title,body,baseRefName,headRefName.
  • 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.
  • 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.
  • Apply the update
  • Use gh pr edit <pr> --title "..." --body "...".

How to use it

Copy the folder

Take fcakyon/update-pr-summary from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.