CtrlK
BlogDocsLog inGet started
Tessl Logo

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

Quality

100%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

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 guides Claude through PR review, CI verification, and release tagging for Spatie packages. It excels in providing concrete CLI commands at every step, clear stop conditions for error cases, and specific domain knowledge (Spatie versioning conventions) that Claude wouldn't otherwise know. The workflow is logically sequenced with appropriate validation checkpoints.

DimensionReasoningScore

Conciseness

The skill is lean and efficient. It doesn't explain what PRs are, what gh CLI is, or how Git works. Every section provides actionable information that Claude wouldn't inherently know (specific versioning rules for Spatie packages, the convention around PHP/Laravel version drops). No wasted tokens.

3 / 3

Actionability

Provides specific, executable gh CLI commands for every step (fetching PR details, reviewing, merging, creating releases). The versioning rules are concrete and specific, including the non-obvious rule that dropping PHP/Laravel support is not a breaking change. Commands are copy-paste ready with clear placeholders.

3 / 3

Workflow Clarity

The workflow is clearly sequenced with four numbered steps. It includes explicit validation checkpoints: CI must be green before merging (step 3), and major version bumps require user approval (step 4). There are clear stop conditions ('inform the user and stop') when CI fails or issues are found, creating proper feedback loops.

3 / 3

Progressive Disclosure

For a skill of this size and scope (~50 lines, single focused task), the content is well-organized with clear sections and subsections. No bundle files are needed as all necessary information fits cleanly in the single file without becoming a wall of text. The versioning rules subsection is appropriately nested under the merge step.

3 / 3

Total

12

/

12

Passed

Description

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 communicates what the skill does (review and merge PRs for Spatie packages), when to use it (with extensive natural trigger terms), and how it operates (gh CLI). It uses proper third-person voice and is concise yet comprehensive, making it easy for Claude to select appropriately from a large skill set.

DimensionReasoningScore

Specificity

Lists specific concrete actions: 'Review and merge GitHub pull requests for Spatie packages.' Also mentions using 'gh CLI for all GitHub operations,' which adds implementation specificity.

3 / 3

Completeness

Clearly answers both what ('Review and merge GitHub pull requests for Spatie packages') and when ('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...') with explicit trigger guidance.

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 highly natural phrases users would actually say.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive: scoped to 'Spatie packages' specifically, focused on PR review/merge operations, and mentions gh CLI. The combination of GitHub PRs + Spatie packages creates a clear niche unlikely to conflict with other skills.

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
freekmurze/dotfiles
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.