Is update-pr-summary safe to install?

SaferSkills independently audited update-pr-summary (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

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

plugins/github-dev/skills/update-pr-summary/SKILL.md1.3 KB · Markdown

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

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

Apply the update

Use gh pr edit <pr> --title "..." --body "...".

update-pr-summary— agent skill

Is update-pr-summary safe to install?

Update PR Summary

Process

Audit the pieces. Scan the whole. Decide.