comprehensive-review-pr-enhance

You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensure PRs follow best practices for clarity, size, and reviewability.

Quality

48%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agent/skills/comprehensive-review-pr-enhance/SKILL.md

Quality

Content

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

The body is short and sectioned, but it functions as a table of contents for content that is not there: the one referenced detail file does not exist in the bundle, and it is referenced under two different paths. What remains is generic directive-level guidance with no examples or templates, plus duplicated framing text.

Suggestions

Fix the broken reference: create the playbook file (or remove the pointer) and use a single consistent path for it in one clearly labeled Resources section instead of three scattered mentions.

Add a concrete example or fill-in template for the PR description output (e.g., a sample summary/scope, what-changed, tests, risks layout) so the guidance is executable without the missing playbook.

Remove the duplicated opening paragraph and the "Context" section that restate the frontmatter description, keeping only guidance Claude does not already know.

Dimension	Reasoning	Score
Conciseness	The body is short but carries real redundancy: the frontmatter description is repeated verbatim as the opening paragraph, the playbook reference appears three times (Instructions, Resources, and the "Knowledge Modules" section), and the "Context" section ("The user needs to create or improve pull requests...") restates the description without adding guidance.	3 / 5
Actionability	The instructions are high-level directives — "Analyze the diff and identify intent and scope", "Summarize changes, tests, and risks clearly" — with no template, example PR description, or concrete structure to execute against; the Output Format lists only section names, and the actual specifics are delegated to a playbook file that is not present in the bundle.	2 / 5
Workflow Clarity	The instruction bullets form a rough sequence (analyze diff, summarize changes, highlight breaking changes, add checklists) and the task is non-destructive so the validation cap does not apply, but there are no checkpoints or feedback steps (e.g., verify the summary matches the diff, confirm test results are real).	3 / 5
Progressive Disclosure	The body points to the playbook via two inconsistent paths — "resources/implementation-playbook.md" in Instructions and "./sub-skills/implementation-playbook.md" in the Knowledge Modules section — and neither file exists in the bundle (there are no resources/, sub-skills/, references/, scripts/, or assets/ directories), leaving navigation broken and the reference duplicated rather than well-signaled.	2 / 5
	Total	10 / 20 Passed

Description

57%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 names a recognizable domain and includes natural PR/review vocabulary, but it is written in second-person role-play voice, contains generic filler actions, and completely lacks a "when to use" trigger clause. It reads as a persona statement rather than a capability-plus-trigger description.

Suggestions

Rewrite in third person and drop the role-play framing: e.g., "Generates and improves pull request descriptions..." instead of "You are a PR optimization expert...".

Add an explicit trigger clause: "Use when writing or improving a PR description, summarizing a diff for review, or preparing release/rollout notes."

Replace vague actions ("automate review processes", "ensure PRs follow best practices") with concrete capabilities such as "draft structured PR summaries, extract test and risk sections from a diff, and flag breaking changes".

Dimension	Reasoning	Score
Specificity	"Generate comprehensive PR descriptions, automate review processes, and ensure PRs follow best practices" mixes one concrete action with two generic ones ("automate review processes", "ensure...best practices"), and the second-person framing "You are a PR optimization expert" incurs the rubric's one-point voice penalty from an otherwise borderline-4 action list.	3 / 5
Completeness	The "what" is reasonably clear (generate PR descriptions, automate review processes), but there is no "Use when..." clause or equivalent trigger guidance anywhere in the description, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	"pull requests", "PR", "PR descriptions", and "code reviews" are natural terms users would say, giving good coverage; common variations like "diff", "change summary", or "PR summary" are missing, so it does not reach comprehensive synonym-level coverage.	4 / 5
Distinctiveness Conflict Risk	The PR-description niche is somewhat specific, but "facilitate efficient code reviews" and "automate review processes" create real overlap with dedicated code-review skills, so a user asking for a review could trigger the wrong skill.	3 / 5
	Total	13 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI
Path: .agent/skills/comprehensive-review-pr-enhance/SKILL.md
Commit: c4a059b

Reviewed: 1 hour ago

Table of Contents

Discovery Implementation Validation

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.