Install any skill in seconds. Free to start, no credit card required.
Get Started Free →athola/pr-review
Reviews pull requests with scope validation, requirements compliance, and line comments.
Passed 13 of 18 test cases with the skill, and 5 of 18 without it.
and 8 more in the full report
10 fixed6 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
You generated findings for PR #50 in .review/findings.json. What command must be executed to verify that all citation locations and verbatim anchors exist in the repo?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies running python plugins/imbue/scripts/citation_verifier.py --findings .review/findings.json --repo-root . | Missed | Passed |
The instructions your model reads when the skill loads.
Review pull/merge requests with discipline: validate against original requirements, prevent scope creep, and route out-of-scope findings to issues on the detected platform.
Platform detection is automatic via leyline:git-platform. Use gh for GitHub, glab for GitLab. Check session context for git_platform:.
A PR review validates scope compliance, not code perfection.
The goal is to validate the implementation meets its stated requirements without introducing regressions. Improvements beyond the scope belong in future PRs.
Every finding must be classified:
| Category | Definition | Action |
|---|---|---|
| BLOCKING | Bug, security issue, or regression introduced by this change | Must fix before merge |
| IN-SCOPE | Issue directly related to stated requirements | Should address in this PR |
| SUGGESTION | Improvement within changed code, not required | Author decides |
| BACKLOG | Good idea but outside PR scope | Create GitHub issue |
| IGNORE | Nitpick, style preference, or not worth tracking | Skip entirely |
test cases passed, vs 5 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.