pr-triage — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited pr-triage (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.
Rank pull requests by urgency, impact, merge risk, and blocking effect so review time goes to the most important work first.
Do not use for deep code review or CI debugging unless explicitly requested.
Preferred tools:
gh CLI or repository connectorOptional gh check:
Get-Command gh -ErrorAction SilentlyContinue
gh auth statusgh, connector data, or a combinationgit status --short
git branch --show-current
git log --oneline --decorate -n 20gh pr list --state open --json number,title,author,updatedAt,isDraft,reviewDecision,mergeStateStatus,statusCheckRollup,labels
gh pr view <pr> --json files,additions,deletions,reviewDecision,mergeStateStatus,statusCheckRollup| Signal | Higher priority when |
|---|---|
| Blocking effect | Other work depends on it |
| Review age | It is stale but still relevant |
| Merge state | It has conflicts or failing required checks |
| Blast radius | It touches public API, auth, data, migrations, or shared infra |
| Size | It is small enough to unblock quickly or too large to ignore |
PR TRIAGE:
Top actions:
1. <PR> - <action> - <reason>
Blocked:
- <PR> - <blocker>
Review now:
- <PR> - <why now>
Stale/defer:
- <PR> - <reason>
Risks:
- <risk needing human judgment>gh data exists when the CLI is missing or unauthenticated.If gh is missing or unauthenticated:
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.