pr-review — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited pr-review (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.
Post targeted inline comments on specific lines and submit a formal review (approve, request changes, or comment).
pr-analysis skill first to understand the PR before reviewingrepo_owner, repo_name, pr_number for the target PRrepo write accesspr-analysis skill to read diff and metadataadd_inline_pr_comment for each specific line that needs feedbackadd_pr_comments for overall remarks not tied to a specific lineupdate_reviews with APPROVE, REQUEST_CHANGES, or COMMENTadd_inline_pr_comment| Parameter | Type | Description |
|---|---|---|
repo_owner | str | GitHub organisation or username |
repo_name | str | Repository name |
pr_number | int | Pull request number |
path | str | File path relative to repo root (e.g. src/app/main.py) |
line | int | Line number in the new file (right side of diff) |
comment_body | str | Markdown comment text |
add_pr_comments| Parameter | Type | Description |
|---|---|---|
repo_owner | str | GitHub organisation or username |
repo_name | str | Repository name |
pr_number | int | Pull request number |
comment | str | Markdown comment text for the overall PR thread |
update_reviews| Parameter | Type | Description |
|---|---|---|
repo_owner | str | GitHub organisation or username |
repo_name | str | Repository name |
pr_number | int | Pull request number |
event | str | One of: APPROVE, REQUEST_CHANGES, COMMENT |
body | str (optional) | Summary body for the review |
| Decision | When to use |
|---|---|
APPROVE | All concerns addressed, code is correct and safe to merge |
REQUEST_CHANGES | Blocking issues found (bugs, security, missing tests) |
COMMENT | Non-blocking feedback or questions, no decision yet |
update_reviews — they are grouped under the same reviewadd_inline_pr_comment for specific code feedback; use add_pr_comments for high-level remarksbody in update_reviews summarising the rationale for the decisiondraft: true)Fixes #42)~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.