CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-pr

Analyze a GitHub pull request including diff, comments, related issues, and local code context

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/review-pr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 strong workflow skill: nearly every operational step has an exact, executable command, validation checkpoints and error-recovery loops are explicit, and the test-coverage and output-structure sections give concrete checklists. The main defects are a missing referenced bundle file (identifier-normalization.md), no worked example of the final review output, and a few trimmable over-explanations.

DimensionReasoningScore

Conciseness

The body is command-driven with no explanation of concepts Claude already knows (e.g., 'gh pr view PR_ID --json ...'), though minor over-explanation could be trimmed: the dependency-impact classifications ('these affect every user' / 'no impact on end users'), the hand-holding cwd verification ('If pwd does not show WORKTREE, run cd WORKTREE and verify again'), and slight redundancy in step 3 ('so the comparison is against the current state' vs. 'always compare against origin/devel regardless'). Not 5 because these padded spots keep it from 'every token earns its place'; not 3 because there is no unnecessary concept explanation overall.

4 / 5

Actionability

Mostly executable guidance with copy-paste-ready commands ('gh pr diff PR_ID', 'python tools/check_dependency_changes.py origin/devel') and explicit exit-code handling ('exits with code 1 (changes detected)... code 2 (conflicts)'). Minor gaps keep it below anchor 5: no worked example of the final review output (only section descriptions), and '<run-id>' retrieval for 'gh run view <run-id> --log-failed' is never specified. Clearly above anchor 3 — nothing is pseudocode or abstract.

4 / 5

Workflow Clarity

Clear numbered sequence (steps 1–9 with sub-steps 7a–7e), explicit validation with stop-on-error ('Stop with an error if the cwd cannot be set'), feedback loops for error recovery (exit-code branching in step 3, 'If any lint check has failed, fetch its logs'), and checklists ('Produce a checklist of required test scenarios'). This matches anchor 5 exactly; the workflow is read-only analysis, so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

Good structure with a well-signaled, one-level-deep, conditionally-loaded reference ('read the linked file ONLY when the PR's diff matches the trigger') pointing to identifier-normalization.md — but that file does not exist in the skill bundle (no references/ directory), so navigation to it breaks. Anchor 4's 'minor organization gaps' fits; not 5 because a promised reference is missing, and not 3 because the main body is well split into sections with only that single gap.

4 / 5

Total

17

/

20

Passed

Description

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

The description is specific and distinct — it names the GitHub PR domain and enumerates concrete analysis targets — but it is incomplete as a trigger: it has no 'Use when...' guidance and misses the most natural user phrasings ('review', 'PR', 'code review'). It also undersells the skill's actual capabilities (CI checks, dependency changes, test coverage, documentation review).

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to review or analyze a pull request, PR, or code review request on GitHub.'

Include the natural synonyms users say — 'review', 'PR', 'code review' — alongside 'GitHub pull request' to improve trigger matching.

Mention the skill's other concrete capabilities (CI lint/mypy status, dependency-change checks, test coverage and documentation review) so the description covers what the skill actually does.

DimensionReasoningScore

Specificity

The description names the domain and enumerates concrete analysis inputs ('including diff, comments, related issues, and local code context') but relies on a single generic action verb ('Analyze') and omits major skill capabilities — dependency checks, CI lint status, test coverage review, documentation coverage. This matches anchor 3 ('1-2 concrete actions, but not comprehensive'); the coverage gaps are more than 'minor', so anchor 4 does not fit.

3 / 5

Completeness

The 'what' is clear ('Analyze a GitHub pull request including diff, comments, related issues, and local code context') but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines. The 'when' is only weakly implied by the domain itself, so anchor 4 ('both what and when') does not fit.

3 / 5

Trigger Term Quality

Good keyword coverage with natural terms ('GitHub pull request', 'diff', 'comments', 'related issues', 'local code context'), but a few natural terms users would actually say are missing: 'review', 'PR', and 'code review'. Better than anchor 3's 'some relevant keywords' because the core domain phrases plus supporting terms are present; not anchor 5 because common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

Mostly distinct: 'Analyze a GitHub pull request' carves out a clear niche with specific inputs, carrying only minor overlap risk with generic code-review or git-analysis skills. Not anchor 5 because without explicit trigger phrases, a request like 'review these changes' could plausibly match a sibling code-review skill; clearly above anchor 3's 'could still overlap with similar skills'.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

dlt-hub/dlt

Path

.claude/skills/review-pr/SKILL.md

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.