Update Pr SummarySAFE
Battle-tested Claude Code, OpenAI Codex, Cursor configs, plugins, hooks and agents with Kimi, MiniMax and GLM API support.
Overview
Battle-tested Claude Code, OpenAI Codex, Cursor configs, plugins, hooks and agents with Kimi, MiniMax and GLM API support.
ae618ef5da66OBSERVED · 2026-10-12What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- 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 body to describe the final change and evidence. Treat extra invocation text as the PR reference and any requested corrections. 1. Read repository guidance and fetch the current body before editing: `gh pr view <pr> --json title,body,baseRefName,headRefName,url`. 2. Review the complete PR diff against its actual base, not this checkout's unrelated HEAD. Use `git diff <remote>/<base>...<head>` when those refs are current, otherwise `gh pr diff <pr>`. Ignore changes outside the PR and collect completed checks relevant to its current head. 3. Read [create-pr](../create-pr/SKILL.md) for title, body, evidence, and visual-hosting guidance. Apply the user's correction to the relevant portion. Preserve uploaded visuals, bot-added context, links, and valid results. An explicit full rewrite still keeps those unless the user asks to remove them. Rewrite stale claims and titles around the final scope. 4. Save the exact body to a temporary file outside the repo. Re-read the remote body just before writing. If it changed, incorporate those edits rather than overwriting them. Apply with `gh pr edit <pr> --title "..." --body-file <path>`. 5. Read back `title,body,url` and compare with the intended edit. Verify that preserved content, fences, tables, and links survived. Open the PR to check media rendering when relevant. Report the PR URL and any remaining evidence or upload gap.
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (3)
.claude/output-styles/adhd-explanatory.md
AGENTS.md
GEMINI.md
Gates applied: no_behavioural_pass.
ae618ef5da66full audit observations/trust-audit/skill/fcakyon__update-pr-summary.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-12 | ae618ef5da66 | SAFE | B | 89 | first audit |
Questions
What does the Update Pr Summary skill do?
Battle-tested Claude Code, OpenAI Codex, Cursor configs, plugins, hooks and agents with Kimi, MiniMax and GLM API support.
Is Update Pr Summary safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Update Pr Summary access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (ae618ef5da66), read on 2026-10-12. The repository is watched, and a new audit runs when it changes — this is the first audit.