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.

75

Quality

93%

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

87%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, well-structured skill that provides concrete, actionable guidance with a ready-to-use PR template and clear categorization rules. The conciseness is excellent — it respects Claude's intelligence while adding genuinely useful domain-specific structure. The main weakness is the lack of validation checkpoints in the workflow, such as verifying the generated description against the actual diff or confirming with the user before finalizing.

Suggestions

Add a validation step in the workflow, e.g., 'Verify the Changes table accounts for all files in the diff stat output' to create a feedback loop between step 1 and step 3.

DimensionReasoningScore

Conciseness

Every section earns its place — the template, checklist rules table, and splitting guidance are all novel information Claude wouldn't inherently know about the user's desired PR format. No unnecessary explanations of what PRs or diffs are.

3 / 3

Actionability

Provides a concrete git command to start, a copy-paste-ready markdown template with realistic examples (OAuth2 PKCE flow), specific threshold numbers (>500 lines, 20 files, 1000 lines), and executable cherry-pick commands for splitting. Fully actionable.

3 / 3

Workflow Clarity

The 5-step workflow is clearly sequenced and logical, but there are no validation checkpoints or feedback loops — e.g., no step to verify the generated description matches the actual diff, no review/confirmation step before finalizing, and no error recovery guidance if the diff is ambiguous or the categorization is wrong.

2 / 3

Progressive Disclosure

Content is well-structured with clear sections (Workflow, Template, Checklist Rules, Splitting, Resources) and appropriately references a single external resource file for advanced helpers. Navigation is straightforward and one level deep.

3 / 3

Total

11

/

12

Passed

Description

100%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that hits all the marks. It provides specific concrete actions, comprehensive natural trigger terms covering common user phrasings, explicit 'Use when' guidance, and a clearly distinct domain. It follows the third-person voice convention and is concise without being vague.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'Generate structured PR descriptions from diffs', 'add review checklists', 'risk assessments', and 'test coverage summaries'. These are all distinct, concrete capabilities.

3 / 3

Completeness

Clearly answers both 'what' (generate structured PR descriptions, add checklists, risk assessments, test coverage summaries) and 'when' with an explicit 'Use when...' clause listing specific trigger phrases.

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: 'write a PR description', 'improve this PR', 'summarize my changes', 'PR review', 'pull request', 'document a diff for reviewers'. Covers both abbreviation (PR) and full form (pull request).

3 / 3

Distinctiveness Conflict Risk

Clearly occupies a distinct niche around PR/pull request descriptions and review documentation. The specific triggers like 'PR description', 'pull request', 'document a diff for reviewers' are unlikely to conflict with other skills like general git or code review skills.

3 / 3

Total

12

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

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.