Use when reviewing a PR, branch, diff, doc, skill, or comment block for wordiness, history or roadmap prose, restated information, or code and tests beyond what the spec asks for.
87%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Review changed prose and code against five rules. The review obeys them too.
gh pr diff and gh api repos/OWNER/REPO/contents/PATH?ref=HEAD_SHA; the review leaves every checkout and ref as it found them.--help, published docs), that copy stays; the finding is that the other copies link to the canonical one.The review is exactly:
**Verdict:** <one sentence: how much should go, and the biggest reason>
1. `path:line` — [rule #] <problem in one sentence>
**Fix:** <replacement text in quotes, "Delete.", or "Link to `path#anchor`.">
2. ...NVIDIA/OpenShell
2e5589b
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.