Claude Cursor Skill

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".

LLM Mart · 0 points · 6 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download fcakyon-claude-codex-settings-plugins_github-dev_skills_update-pr-summary-4632eb3.zip · 0 KB

fcakyon/claude-codex-settings 1155 110 forks Apache-2.0 Updated 2d ago

Part of fcakyon/claude-codex-settings — 83 skills

Install

skills CLI npx skills add https://github.com/fcakyon/claude-codex-settings/tree/main/plugins/github-dev/skills/update-pr-summary

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install fcakyon-claude-codex-settings@llmmart

Git git clone https://github.com/fcakyon/claude-codex-settings.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole fcakyon/claude-codex-settings collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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 "...".

Files (claude-codex-settings)

SKILL.md 1.5 KB

---
name: update-pr-summary
description: 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".
---

# 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. **Apply the update**
   - Use `gh pr edit <pr> --title "..." --body "..."`.