Agent-Skills.md

Agent Skills: 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".

UncategorizedID: fcakyon/claude-codex-settings/update-pr-summary

Repository

fcakyon/claude-codex-settings
fcakyonLicense: Apache-2.0
1,155110

Install this agent skill to your local

pnpm dlx add-skill https://github.com/fcakyon/claude-codex-settings/tree/HEAD/plugins/github-dev/skills/update-pr-summary

Skill Files

Browse the full folder contents for update-pr-summary.

Download Skill

Loading file tree…

plugins/github-dev/skills/update-pr-summary/SKILL.md

Skill Metadata

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