Skip to content
Back to skills

Update Pr Summary

ASecurity

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

  • 1,161 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 27, 2026
developmentgogitapi

Works with

  • api

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add fcakyon/claude-codex-settings --skill update-pr-summary --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Update Pr Summary?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Update Pr Summary
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/fcakyon-update-pr-summary/badge)](https://www.skillsdirectory.com/skills/fcakyon-update-pr-summary)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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.
   - Start the title with a capital letter and a verb, with no `fix:` or `feat:` prefix.
   - Use plain language. Avoid jargon and internal shorthand unless an exact command or tool name is needed.
   - Keep the body to a single short section.
   - Include 1-2 sentences, a few bullets, and one usage snippet or before/after example when helpful.
   - Do not include test plans, changed file lists, or line-number links.

4. **Apply the update**
   - Use `gh pr edit <pr> --title "..." --body "..."`.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…