Content
75%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A thorough, highly actionable PR-review skill with executable commands for both GitHub and GitLab and a clear six-step workflow. Its main weaknesses are length/redundancy and a monolithic structure with limited error-recovery feedback loops.
Suggestions
Deduplicate the diff-fetching commands: the standalone "Fetching the Diff" section repeats what Step 1 already covers — consolidate into one place to trim tokens.
Add explicit validation/feedback loops (e.g. "if CI checks fail, report and stop"; "if coverage delta < threshold, re-run with --coverage and surface missing lines") to lift workflow clarity.
Consider moving the 30+ item checklist and the security/performance grep catalog into a references/ file linked from SKILL.md so the main file reads as an overview pointing to detailed materials.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is information-dense and avoids explaining concepts Claude already knows, but at ~390 lines it includes redundancy — e.g. the "Fetching the Diff" section duplicates commands restated in "Step 1 — Fetch Context" — so it could be tightened; fits the "mostly efficient but includes some unnecessary explanation or could be tightened" anchor rather than a 4. | 3 / 5 |
Actionability | Copy-paste-ready executable commands throughout — gh/glab CLI invocations and concrete grep patterns for SQL injection, secrets, XSS, N+1, etc. — cover the common review cases, matching the "fully executable; copy-paste ready" anchor. | 5 / 5 |
Workflow Clarity | A clear six-step sequence (Fetch Context → Blast Radius → Security → Coverage → Breaking Changes → Performance) plus CI-status and coverage-rule checkpoints and a 30+ item checklist; not a 5 because explicit error-recovery feedback loops (validate → fix → retry) are largely absent beyond the coverage block rule. | 4 / 5 |
Progressive Disclosure | Well-organized with clear section headers and logical navigation, and no bundle files exist so all content is appropriately inline; the gap keeping it from 5 is the monolithic ~390-line manual where the command catalog or checklist could be split into one-level-deep reference files. | 4 / 5 |
Total | 16 / 20 Passed |