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".
Profile →npx skills add fcakyon/claude-codex-settings --skill update-pr-summary --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 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. **A
- Process
What does the update-pr-summary skill do?
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".
How do I install it?
Run `npx skills add fcakyon/claude-codex-settings --skill update-pr-summary --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From fcakyon/claude-codex-settings, a repository with 967 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.