CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

2.04x
Quality

87%

Does it follow best practices?

Impact

100%

2.04x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 solid, highly actionable body: concrete commands, a ready-to-use template, and precise checklist rules tied to diff categories. The main issues are a dangling reference to a nonexistent resources/implementation-playbook.md, the absence of any verification checkpoint in the workflow, and a small amount of generic boilerplate in Limitations.

Suggestions

Fix the Resources section: either add the referenced resources/implementation-playbook.md to the bundle or remove the pointer, since the file does not currently exist.

Add a lightweight verification step to the workflow, e.g. after step 2 confirm every file from the --stat output is categorized before generating the description.

Trim the generic Limitations boilerplate and the When-to-Use section that duplicates the frontmatter description to reclaim tokens.

DimensionReasoningScore

Conciseness

The body is efficient — concrete commands, a compact template, and a dense checklist table — but the "Limitations" section is generic boilerplate ("Use this skill only when the task clearly matches the scope described above") and "When to Use" restates the frontmatter description. Not 5: these padded sections could be trimmed without losing skill-specific value.

4 / 5

Actionability

Fully executable guidance throughout: `git diff <base>...HEAD --stat`, a copy-paste-ready markdown template with worked example rows, specific per-category checklist items, and concrete split commands (`git checkout -b feature/part-1`, `git cherry-pick`) with explicit thresholds (20 files / 1000 lines). Not 4: there are no gaps in the common-case coverage.

5 / 5

Workflow Clarity

A clear 5-step numbered workflow with concrete commands and unambiguous outputs. Not 5: no validation or verification checkpoint exists (e.g., confirming every changed file from the --stat output is categorized before generating); not 3: the sequence is far more concrete than the bare-steps anchor-3 example, and the non-destructive nature of the task makes missing checkpoints a minor rather than disqualifying gap.

4 / 5

Progressive Disclosure

Well-organized sections with content appropriately placed inline (template, checklist table) and a single, clearly signaled one-level reference in a Resources section. Not 5: the sole referenced file `resources/implementation-playbook.md` does not exist in the bundle — the pointer is dangling, so navigation to the referenced material fails.

4 / 5

Total

17

/

20

Passed

Description

88%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 that clearly states concrete capabilities and pairs them with explicit, natural trigger phrases in the recommended good-example pattern. The only weaknesses are a few missing synonyms ("merge request", "PR summary") and the "PR review" trigger's ambiguity versus code-review skills.

DimensionReasoningScore

Specificity

Lists four concrete actions — "Generate structured PR descriptions from diffs", "add review checklists", "risk assessments", "test coverage summaries" — giving comprehensive coverage of the skill's capabilities. Not 4: there is no meaningful gap in the action coverage relative to what the skill does.

5 / 5

Completeness

Explicitly answers both what ("Generate structured PR descriptions from diffs, add review checklists, risk assessments, and test coverage summaries") and when ("Use when the user says 'write a PR description'...") with concrete trigger phrases, matching the anchor-5 pattern exactly.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ("write a PR description", "improve this PR", "summarize my changes", "pull request") with the PR/pull-request synonym pair covered. Not 5: common variations like "merge request", "PR summary", or "open a PR" are missing.

4 / 5

Distinctiveness Conflict Risk

The PR-description-from-diff niche is clear and mostly distinct, but the trigger "PR review" would naturally be said by a user wanting a code review, and "summarize my changes" overlaps with commit-message skills. Not 5: these are real, if minor, overlap risks with closely related skills.

4 / 5

Total

18

/

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/comprehensive-review-pr-enhance/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.