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.

75

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An excellent, tight workflow skill: executable commands at every step, explicit stop/validation checkpoints around the destructive merge, and a clean single external reference for shared lanes. No meaningful weaknesses to address.

DimensionReasoningScore

Conciseness

Lean and purposeful throughout: executable gh commands with no padding, no explanation of what a PR or gh is, and only non-obvious guidance such as thanking the issue author vs. the PR author.

5 / 5

Actionability

Fully executable, copy-paste-ready gh commands cover every step (pr view/diff, review --request-changes, merge --squash --delete-branch, issue/pr comment, release list/create) with concrete flags.

5 / 5

Workflow Clarity

Clear 6-step sequence with explicit validation checkpoints and stop conditions: report-only review, 'If there are issues... and stop', 'If CI is failing or pending... stop', and 'Never tag a release unless I explicitly ask'.

5 / 5

Progressive Disclosure

Single well-organized SKILL.md with one clearly signaled one-level-deep reference to ~/.claude/skills/review-code/references/lanes.md for lane definitions; no nested or buried references.

5 / 5

Total

20

/

20

Passed

Description

86%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-structured description with explicit trigger guidance and good keyword coverage. It could push specificity higher by naming the full action set (verify CI, thank author, optional release) rather than only review and merge.

Suggestions

Expand the 'what' clause to surface the full action set, e.g. 'Review and merge GitHub pull requests for Spatie packages: verify CI, run review lanes, merge, and thank the author.'

Consider noting the relationship to the review-code skill in the description to reduce trigger overlap ambiguity.

DimensionReasoningScore

Specificity

Names the domain (GitHub PRs for Spatie packages) and two concrete actions ('Review and merge'), plus the tool ('Uses gh CLI'), but does not enumerate the fuller set of actions (verify CI, thank author, release) that the body covers.

3 / 5

Completeness

Explicitly answers both 'what' (review and merge GitHub PRs for Spatie packages via gh CLI) and 'when' with concrete trigger phrases in an explicit 'Use when...' clause.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage with synonyms and the slash command: 'review a PR', 'review a pull request', 'merge a PR', 'GitHub PR URL', 'review this PR', 'check this pull request', 'merge this', and '/review-pr'.

5 / 5

Distinctiveness Conflict Risk

Scoped to Spatie packages with a distinct '/review-pr' trigger, but overlaps with the related review-code skill it delegates to, creating minor conflict risk.

4 / 5

Total

17

/

20

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.

Validation16 / 16 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.