CtrlK
BlogDocsLog inGet started
Tessl Logo

comprehensive-review-pr-enhance

Generate structured PR descriptions from diffs, add review checklists, risk assessments, and test coverage summaries. Use when the user says "write a PR description", "improve this PR", "summarize my changes", "PR review", "pull request", or asks to document a diff for reviewers.

81

2.61x
Quality

82%

Does it follow best practices?

Impact

68%

2.61x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

Well-structured and largely actionable content with a useful template and concrete git commands. Main weaknesses are the lack of validation checkpoints in the workflow and a 'Resources' pointer to a file that is not present in the bundle.

Suggestions

Add an explicit verification checkpoint to the workflow (e.g., re-run `git diff --stat` and confirm the categorization matches before generating the description), since the current 5 steps have no validate/feedback step.

Either create `resources/implementation-playbook.md` or remove the 'Resources' section — the referenced file does not exist in the bundle, leaving a broken navigation link.

Tighten the generic 'Limitations' boilerplate to skill-specific boundaries only, or fold it into 'When to Use' to recover token budget.

DimensionReasoningScore

Conciseness

Mostly lean — no padding explaining what a PR is, and sections like the template and checklist table earn their place — though the generic 'Limitations' boilerplate ('Stop and ask for clarification if ...') could be trimmed. Not a 5 because of that mild boilerplate.

4 / 5

Actionability

Provides executable commands ('git diff <base>...HEAD --stat', 'git checkout -b', 'git cherry-pick'), a copy-paste PR template, and concrete per-category checklist rules. Not a 5 because 'Categorise changes' is stated abstractly without a concrete method.

4 / 5

Workflow Clarity

The 5-step workflow is clearly sequenced with concrete commands, but there are no validation/verification checkpoints or feedback loops. This sits between anchors 3 and 4; the absence of any verify step pulls it to 3.

3 / 5

Progressive Disclosure

Good section structure with one one-level-deep reference ('resources/implementation-playbook.md'), but that referenced file does not exist in the bundle — a broken navigation target that undermines discovery. Not a 4 because the missing reference is more than a minor gap.

3 / 5

Total

14

/

20

Passed

Description

100%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 description: concrete capabilities, explicit 'Use when' triggers with natural phrasing, and a well-scoped niche. Third-person imperative voice is used correctly with no over-claims.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Generate structured PR descriptions from diffs, add review checklists, risk assessments, and test coverage summaries' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both what (first sentence) and when ('Use when the user says ...') with concrete trigger phrases, matching the 5 anchor exactly.

5 / 5

Trigger Term Quality

Lists natural phrases users actually say — 'write a PR description', 'improve this PR', 'summarize my changes', 'PR review', 'pull request' — with good synonym coverage.

5 / 5

Distinctiveness Conflict Risk

PR-description generation is a clear niche with distinct triggers; minimal overlap risk with other skills.

5 / 5

Total

20

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
sickn33/agentic-awesome-skills
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.