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.
100
100%
Does it follow best practices?
Impact
Pending
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 description is concise yet comprehensive.
| 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 high-quality skill that efficiently communicates a clear PR review and merge workflow with specific gh CLI commands. It excels at encoding domain-specific knowledge (Spatie versioning conventions, PHP/Laravel support policy) that Claude wouldn't otherwise know. The safety guardrails around major version bumps and CI checks are well-placed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every section serves a purpose, there's no explanation of what PRs are or how gh CLI works, and the versioning rules convey domain-specific knowledge Claude wouldn't inherently know (e.g., dropping PHP/Laravel support is NOT a breaking change). | 3 / 3 |
Actionability | Provides specific, executable gh CLI commands for every step (fetching PR details, reviewing, merging, creating releases). The versioning rules are concrete with specific examples of version bump patterns. | 3 / 3 |
Workflow Clarity | Clear 4-step sequential workflow with explicit validation checkpoints: CI must be green before merging, issues trigger a stop-and-comment action, major version bumps require explicit user approval. The feedback loops for error cases (failing CI → stop, issues found → request changes and stop, version doubt → ask user) are well-defined. | 3 / 3 |
Progressive Disclosure | For a skill of this size (~50 lines), the content is well-organized with clear hierarchical sections and subsections (versioning rules nested under merge and release). No need for external file references given the scope, and the structure is easy to scan. | 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
2c6f6e8
- 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.