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.

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

Concise and largely actionable with good structure, but it lacks validation/feedback steps for batch operations and points to a resource file that does not exist in the bundle.

Suggestions

Add explicit validation checkpoints to the workflow (e.g., 'verify git diff captured all intended files before generating the description', 'confirm checklist items map to actual changed categories') and a fix-retry loop for the large-PR splitting step.

Resolve the dangling reference: either create resources/implementation-playbook.md (and reference it from a standard bundle directory) or remove the Resources entry until the file exists.

Add concrete verification commands for the generated output (e.g., a check that the template's 'Breaking?' answer is consistent with the diff, or a command to re-run --stat to confirm scope) to lift actionability to fully executable.

DimensionReasoningScore

Conciseness

Lean body of tables, a copy-paste template, and git commands with no padding or re-explanation of concepts Claude already knows; every section earns its place.

5 / 5

Actionability

Provides concrete executable commands and a ready template with explicit thresholds (>500 lines, >20 files/1000 lines), but lacks executable validation/verification commands, leaving a minor gap.

4 / 5

Workflow Clarity

The 5-step sequence is clear, but there are no validation checkpoints or a fix-retry loop for the destructive/batch operations (cherry-picking PR splits, generating review artifacts); per the rubric this caps the score at 3.

3 / 5

Progressive Disclosure

Sections are well organized and there is a one-level reference to 'resources/implementation-playbook.md', but that referenced file is not present in the bundle (no references/ or resources/ directory exists), leaving a broken/dangling reference.

3 / 5

Total

15

/

20

Passed

Description

92%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, an explicit trigger clause, and a well-scoped niche with low conflict risk. Only minor room to add a few more trigger synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'structured PR descriptions from diffs', 'review checklists', 'risk assessments', and 'test coverage summaries' — covering the skill's capabilities comprehensively.

5 / 5

Completeness

Explicitly answers both 'what' (generate descriptions, checklists, risk and coverage summaries) and 'when' via a concrete 'Use when the user says...' clause with multiple trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users actually say ('write a PR description', 'improve this PR', 'summarize my changes', 'PR review', 'pull request'); a few common synonyms or phrasings are absent, so it sits just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (PR descriptions from git diffs) with distinctive triggers, making overlap with unrelated skills minimal.

5 / 5

Total

19

/

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
administrakt0r/AI-Agents-Safe-Coding-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.