pr-summary-for-stakeholders — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited pr-summary-for-stakeholders (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.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Ask the user for one of:
https://github.com/org/repo/pull/123)If a PR URL is provided and the GitHub CLI (gh) is available, run:
gh pr view <PR_NUMBER> --json title,body,additions,deletions,changedFiles
gh pr diff <PR_NUMBER>If gh is not available, ask the user to paste the diff or describe the changes.
Before writing, confirm the audience:
Default to "executive" if not specified.
Use exactly this structure. Fill every field. Do not skip any field.
PR Summary — [PR title or brief description]
What changed:
[1-2 sentences maximum. Plain language. No file names, function names,
or technical terms. Describe the change as a user or business observer would.]
Why it matters:
[1-2 sentences. Business value, user benefit, or risk reduction.
Quantify if possible: "reduces processing time by ~30%", "enables X"]
Risk level: [Low / Medium / High]
[One sentence justification. What could go wrong and how likely is it?]
What to monitor after release:
[Specific metrics or behaviors to watch. Or "Nothing additional required."
Never leave this blank — always name at least one thing.]Before sending the summary, verify:
If any check fails, rewrite that section before outputting.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.