pr-summary
From the author
Refresh the current pull request description from its net changes, following the repository's PR template, when asked to update or write the PR summary. Works in any Scenario repository, whatever its default branch.
Install
npx skills add scenario-labs/skills --skill pr-summary -a claude-code
Installs to .claude/skills/pr-summary/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 88
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- update-pr-summaryfcakyon/claude-codex-settingsThis 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".Productivity★ 1.2K
- gh-create-prCherryHQ/cherry-studioCreate or update GitHub pull requests using the repository-required workflow and template compliance. Use when asked to create/open/update a PR so the assistant reads `.github/pull_request_template.md`, fills every template section, preserves markdown structure exactly, and marks missing data as N/A or None instead of skipping sections.Legal★ 52.9K
- pr-descriptionmohitagw15856/pm-claude-skillsWrite a clear pull-request description that gets reviewed fast and merged with confidence, from a git diff, branch summary, or commit list. Use when opening a PR, summarizing a change for review, documenting code changes, or asked to write a PR/merge-request description. Produces a structured PR: what changed and why, how it was tested, risk and rollout, and a focused reviewer guide — so the reviewer understands intent before reading a single diff line.Writing★ 1.5K
- call-summaryanthropics/knowledge-work-pluginsTurn a call transcript or call notes into a customer follow-up email draft, an internal chat summary, and proposed CRM updates. Use when the user says "call summary", "follow up on my [company] call", "summarize my call with [account]", "write the recap", "process this transcript", "process my call notes", "capture the objections and next steps", or pastes rough notes or a transcript after a discovery, demo, or negotiation call.OfficialProductivity★ 31.3K
- open-prpascalorg/editorOpen or update a pull request on pascalorg/editor from the current branch, describing only what the branch actually did. Use when the user asks to open/create a PR, push and PR, or ship a branch in the editor repo.Writing★ 25K
- scenario-reportscenario-labs/skillsUse when a Scenario user wants to report a bug or request a change, on the public tracker at github.com/scenario-labs/skills or by email to [email protected]: turning a failed generation, MCP tool error, or unclear skill into a reproducible report, collecting trace ids with diagnostics_run, stripping keys, signed asset URLs, and personal data, asking before sharing a team or project id, or building a prefilled issue URL. Keywords: file an issue, feature request, feedback.Productivity★ 1.1K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in