pr-review-canvas — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited pr-review-canvas (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.
Turn an unstructured diff into a structured review map: what changed, why it matters, where to look first, and what to be careful about. Helps reviewers focus attention rather than read everything.
# If PR number is known:
gh pr diff <number>
# If on the branch:
git diff main...HEAD --stat
git diff main...HEADAlso fetch the PR description:
gh pr view <number>Assign each file to one category:
| Category | What it means |
|---|---|
| Feature | New user-visible behaviour |
| Fix | Bug correction |
| Refactor | Structure change, no behaviour change |
| Config | Environment, build, or tooling config |
| Test | Test-only changes |
| Infra | CI, Docker, deployment |
| Docs | Documentation or comments only |
## PR Canvas: <PR title>
### Summary
<2-3 sentences: what this PR does and why>
### Change map
| File / Area | Category | Lines ± | Risk | Reviewer note |
|-------------|----------|----------|------|---------------|
| src/foo.ts | Feature | +120/-30 | Med | Core logic change — review carefully |
| tests/foo.test.ts | Test | +80 | Low | Covers happy path + 2 edge cases |
| config/env.example | Config | +3 | Low | New env var — check deployment runbook |
### Risk sections (read these first)
1. <file>:<line-range> — <reason it's risky>
2. ...
### What's NOT in this PR (but might be expected)
- <missing tests for X>
- <no migration for schema change>
- ...
### Suggested review order
1. <file or area to read first>
2. ...Automatically flag:
main/master branch protection files..env, credential configs).Print the reviewer map to chat. If the user asks, also write it as PR_CANVAS.md in the repo root (gitignored by default).
Structured reviewer map with change categorization, risk flags, and suggested review order.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.