review-pr
Review and merge GitHub pull requests for Spatie packages. Use when asked to review a PR, review a pull request, merge a PR, or when given a GitHub PR URL to review. Also triggers on 'review this PR,' 'check this pull request,' 'merge this,' or '/review-pr'. Uses gh CLI for all GitHub operations.
80
100%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its scope (reviewing and merging PRs for Spatie packages), provides extensive natural trigger terms covering common user phrasings, and explicitly states both what it does and when to use it. The mention of gh CLI adds useful implementation context. The scoping to Spatie packages makes it highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Review and merge GitHub pull requests for Spatie packages.' Also mentions the tooling used ('gh CLI for all GitHub operations'), which adds specificity. | 3 / 3 |
Completeness | Clearly answers both 'what' (review and merge GitHub pull requests for Spatie packages using gh CLI) and 'when' (explicit 'Use when...' clause with multiple trigger scenarios and phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'review a PR', 'review a pull request', 'merge a PR', 'GitHub PR URL', 'review this PR', 'check this pull request', 'merge this', '/review-pr'. These are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — scoped to 'Spatie packages' specifically, focused on GitHub PR review/merge operations, and mentions gh CLI. Unlikely to conflict with general code review or other GitHub skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that efficiently encodes a complete PR review and release workflow with concrete CLI commands, clear sequencing, and appropriate safety guardrails (especially around major version bumps). The domain-specific knowledge about Spatie package versioning conventions (e.g., dropping PHP/Laravel support not being breaking) adds genuine value. The content is concise, actionable, and well-structured throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. It doesn't explain what GitHub PRs are, what `gh` CLI is, or how merging works conceptually. Every section provides actionable information that Claude needs for this specific workflow. The versioning rules section earns its place by encoding domain-specific knowledge (e.g., dropping PHP/Laravel support is NOT a breaking change). | 3 / 3 |
Actionability | Provides concrete, executable `gh` CLI commands at every step — fetching PR details, posting review comments, merging, checking releases, and creating tags. The JSON fields to inspect are specified, and the versioning rules give specific, actionable decision criteria with examples. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced (fetch → review → check CI → merge/release) with explicit validation checkpoints: stop if issues found (step 2), stop if CI is failing (step 3), and never tag a major bump without user approval (step 4). The feedback loops are appropriate — review issues trigger a request-changes comment and halt, CI failures halt, and version ambiguity triggers a user prompt. | 3 / 3 |
Progressive Disclosure | For a skill of this scope and length (~50 lines of meaningful content), the content is well-organized into clear sections without being monolithic. There are no bundle files, but none are needed — the skill is self-contained and appropriately sized. The versioning rules subsection is a good structural choice rather than inlining it into the merge step. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- freekmurze/dotfiles
- Commit
3974caa
- Reviewed
Table of Contents
Is this your skill?
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.