CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

git-pr-review

Generate a concise and structured PR description from commit history with minimal token usage

Quality

76%

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 ./.agents/skills/git-pr-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

90%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-crafted, token-efficient instruction skill: it provides an exact command, concrete decision rules for noise filtering and grouping, a strict output format, and a worked example. Its only weaknesses are the absence of any output-validation/feedback step and a slightly muddled heading hierarchy inside Step 6.

Suggestions

Add a lightweight validation step after building the output, e.g., 'Re-check: title ≤ 72 chars, total 120–180 words, no noise commits mentioned; trim and re-check if exceeded' — this would add a feedback loop and lift workflow clarity.

Fix the heading hierarchy inside Step 6 by demoting '## Title' and '## Description Format (STRICT)' to '####' level (or folding them into the step text) so section structure stays unambiguous.

State how to detect or override the base branch when it is not 'main' (e.g., check 'git branch' output or accept a base argument) to close the one gap in the command guidance.

DimensionReasoningScore

Conciseness

The body is lean throughout — 'DO NOT scan full diffs initially', the exact 'git log --no-merges --pretty=format:"%h|%s" main..HEAD' command, and terse output rules ('No fluff', 'No emojis') with zero explanation of concepts Claude already knows. Only the decorative '---' separators between every small section add minor token overhead, keeping it just at anchor 5 rather than clearly below it.

5 / 5

Actionability

Guidance is copy-paste ready: the exact git log command, explicit noise filters ('merge', 'lint / format', 'console.log removal'), concrete type-inference mappings ('"add", "create" → feat'), a strict output template ('max 72 chars', 'Max ~120–180 words total'), and a full worked example output. This matches 'fully executable; copy-paste ready commands; specific examples cover the common cases', and the one placeholder command 'git show <hash>' is inherently variable.

5 / 5

Workflow Clarity

Six steps are clearly sequenced (identify range → pre-process → remove noise → group → conditional diff inspection → build output) with a conditional checkpoint ('ONLY IF commit message is vague'). However, there is no validation of the produced output (e.g., checking the 120–180 word budget) or feedback loop for revising a poor draft, which is the 'minor validation gaps' of anchor 4 rather than anchor 5's 'explicit validation steps; feedback loops'.

4 / 5

Progressive Disclosure

The skill is self-contained with no bundle files, and content is appropriately inline with clearly labeled sections ('When to Use', 'Untrusted Input Rules', 'Steps', 'Limitations'). A minor organization flaw: top-level '## Title' and '## Description Format (STRICT)' headings are nested inside '### 6. Build PR output', muddying the hierarchy — anchor 4's 'minor organization gaps' rather than anchor 5's clean, easy navigation.

4 / 5

Total

18

/

20

Passed

Description

53%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 communicates a single concrete capability clearly and in third person, but it reads as a bare minimum: no usage trigger, sparse natural keywords ('pull request' never spelled out), and only one stated action. It is serviceable yet below the quality of the reference good examples, which pair a capability list with an explicit 'Use when...' clause.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user asks to draft, summarize, or write a PR/pull request description from commits.'

Spell out 'pull request' alongside 'PR' and include a synonym or two (e.g., 'summarize commit history') so natural user phrasings match.

Mention one or two more concrete capabilities (e.g., grouping commits by module, filtering noise commits) to strengthen specificity and distinctiveness.

DimensionReasoningScore

Specificity

'Generate a concise and structured PR description from commit history' names the domain and one concrete action — matching anchor 3 ('Names domain and 1-2 concrete actions, but not comprehensive'). It does not list several specific actions (grouping commits, filtering noise, drafting titles), so it falls short of anchor 4, while 'minimal token usage' is a modifier, not a capability.

3 / 5

Completeness

The 'what' is clear (generate a structured PR description from commit history), but there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description. Per the judging guidelines a missing 'Use when' clause caps completeness at 3, which is exactly anchor 3 ('clear what but when is missing').

3 / 5

Trigger Term Quality

'PR description' and 'commit history' are natural phrases, but common variations are missing — 'pull request' is never spelled out and related phrasings like 'release notes' or 'summarize commits' are absent. This matches anchor 3 ('Some relevant keywords but missing common variations or synonyms') rather than anchor 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

'PR description from commit history' carves a fairly distinct niche with minor overlap risk against closely related skills like commit-message generation or general code review — matching anchor 4 ('Mostly distinct; minor overlap risk with closely related skills'). It is not anchor 5 because the thin trigger set ('PR description', 'commit history') doesn't clearly separate it from those neighbors.

4 / 5

Total

13

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

BigSimmo/Communication

Path

.agents/skills/git-pr-review/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.