pr-analysis — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited pr-analysis (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.
Retrieve and synthesise PR metadata and code changes to understand what a pull request does, why, and how.
repo_owner, repo_name, and pr_number for the target PRrepo read accessget_pr_content to get title, description, author, state, base/head branches, and labelsget_pr_diff to get the raw unified diff (patch format) of all changed filesget_pr_content| Parameter | Type | Description |
|---|---|---|
repo_owner | str | GitHub organisation or username |
repo_name | str | Repository name |
pr_number | int | Pull request number |
Returns: PRContent — title, body, author, state, draft status, base/head refs, labels, mergeable state.
get_pr_diff| Parameter | Type | Description |
|---|---|---|
repo_owner | str | GitHub organisation or username |
repo_name | str | Repository name |
pr_number | int | Pull request number |
Returns: raw patch string (unified diff format). Each file section starts with diff --git a/... b/....
When summarising a PR, cover:
get_pr_content before get_pr_diff — metadata gives context for interpreting the diffdraft: true) is not ready for merge review — note this in the analysismergeable is false or null, flag merge conflicts before proceeding~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.