CtrlK
BlogDocsLog inGet started
Tessl Logo

review-github-pr

Review a GitHub pull request by summarizing its diff and key design decisions. Use when the user wants to review a PR, understand changes in a branch, or get a code review summary. Trigger keywords - review PR, review pull request, summarize PR, summarize diff, code review, review branch, PR summary, diff summary.

68

Quality

84%

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

82%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.

A well-structured, highly actionable review workflow with concrete commands and clear branching logic. Minor gains available in trimming the verbose formatting guidance and splitting reference material out of the main file.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence, using concrete commands without explaining what a PR is; minor padding exists in the lengthy Potential Concerns formatting guidance and the duplicated Useful Commands Reference table.

4 / 5

Actionability

It provides copy-paste-ready, fully executable commands (gh pr list/view/diff, git fetch, git diff) covering the primary path plus fallbacks and large-diff handling.

5 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced with explicit decision branches (PR number vs branch, found/multiple/none), but it lacks explicit validation feedback loops; acceptable since the task is read-only summarization.

4 / 5

Progressive Disclosure

Content is well-organized into clear sections within a single self-contained file with no nested references, though the ~175-line body and the inlined commands table/examples could be split out for tighter navigation.

4 / 5

Total

17

/

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, complete description with explicit what/when structure and a rich keyword list. Slightly limited in action specificity and a touch of overlap risk from the generic 'code review' phrasing.

DimensionReasoningScore

Specificity

The description names the domain (GitHub PR review) and 1-2 concrete actions ('summarizing its diff and key design decisions'), but coverage is not comprehensive enough to reach the several-action anchors above.

3 / 5

Completeness

It explicitly answers both what ('Review a GitHub pull request by summarizing its diff and key design decisions') and when ('Use when the user wants to review a PR...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

The 'Trigger keywords' clause enumerates a comprehensive set of natural phrases users would say ('review PR', 'review pull request', 'summarize PR', 'summarize diff', 'code review', 'review branch', 'PR summary', 'diff summary'), including synonyms.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (GitHub PR review) with distinct triggers, but the generic 'code review' term creates minor overlap risk with other review-oriented skills.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
NVIDIA/OpenShell
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.