/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".
$ npx -y skills add fcakyon/claude-codex-settings --skill update-pr-summary --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/update-pr-summary
Context preview
The summary Claude sees to decide when to auto-load this skill.
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".
SKILL.md
update-pr-summary.SKILL.mdname: 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 "..."`.
Read more
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 "..."`.
Battle-tested Claude Code, OpenAI Codex, Cursor configs, plugins, hooks and agents with Kimi, MiniMax and GLM API support.
Repo: fcakyon/claude-codex-settings
Other skills on claude-codex-settings.
- /adhd-output-style
This skill should be used when the user asks for "ADHD output", "fewer output tokens", "short numbered steps", "limited working memory formatting", or explicitly invokes "adhd-output-style".
Open skill - /agent-browser
Agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth,
Open skill - /electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an
Open skill - /docx
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting
Open skill - /pdf
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms,
Open skill - /pptx
Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used
Open skill