review-pr — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited review-pr (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.
Review the pull request: $ARGUMENTS
Follow this process:
why-no-hook: review workflow guidance; each step requires reading the PR and judging code quality / intent.
gh pr view $ARGUMENTS --json title,body,files,commits,additions,deletions,baseRefName,headRefName (review-time: see section note)gh pr diff $ARGUMENTS to see all changes (review-time: see section note)(review-time: see section note)gh), a linked issue, or a spec under .claude/state/specs/ - and check the diff against it, ideally in a parallel sub-agent so it does not pollute the main review context. When the spec has checked criteria, run the Spec Verifier for this pass: (a) requirements asked for but missing or partial; (b) behaviour in the diff nobody asked for (scope creep); (c) requirements that look implemented but wrong. Quote the spec line for each finding and place it in the severity buckets below. If there is no spec, skip this pass and note it. (review-time: see section note)~/.agents/rules/agent-routing.md) (review-time: see section note)(review-time: see section note)(review-time: see section note)## Summary
<1-2 sentence overall assessment>
## Verdict: APPROVE / REQUEST_CHANGES / NEEDS_DISCUSSION
<reason>
## Findings
### BLOCKER (must fix before merge)
- **[file:line]** - Description. Why it matters. Suggested fix.
### ISSUE (should fix, may approve with commitment to follow-up)
- **[file:line]** - Description. Recommendation.
### SUGGESTION (take it or leave it)
- **[file:line]** - Description. Alternative approach.
### NIT (style/preference, non-blocking)
- **[file:line]** - Description.
### PRAISE (good patterns worth highlighting)
- **[file:line]** - What's done well and why.If no $ARGUMENTS provided, review changes in the current branch against the base branch using git diff main...HEAD.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.