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

55%

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

Quality

Content

53%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 skill body is concise and reasonably well-organized but offers only abstract instructional bullets with no executable examples, templates, or commands, and its single external reference points to a file that does not exist in the bundle. Workflow sequencing is present but lacks validation checkpoints.

Suggestions

Provide at least one concrete, copy-paste-ready artifact (a PR description template or a sample generated summary) so the guidance is executable rather than abstract.

Fix the broken reference: either create resources/implementation-playbook.md or remove the reference to it, since progressive_disclosure is capped at 2 while the link is dead.

Add an explicit validation/review checkpoint in the workflow (e.g. 'Verify the generated description covers every diff hunk before presenting') to lift workflow clarity above 3.

Dimension	Reasoning	Score
Conciseness	The body is brief and well-sectioned with minimal padding, though the Context section repeats the description and the opening line restates the frontmatter, which could be trimmed.	4 / 5
Actionability	Instructions are concrete-ish bullet steps ('Analyze the diff', 'Highlight breaking changes') but contain no executable code, commands, or templates, leaving Claude to infer the actual mechanics.	3 / 5
Workflow Clarity	A rough sequence exists via the Instructions and Output Format sections, but there are no validation checkpoints; since PR authorship is not a destructive/batch operation the cap does not apply, yet the implicit checkpoints still keep this at the listed-steps-with-gaps level.	3 / 5
Progressive Disclosure	The body references 'resources/implementation-playbook.md' for detailed templates, but no such bundle file or resources/ directory exists in the skill, so the reference is broken and not one level deep as required.	2 / 5
	Total	12 / 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 clearly conveys the PR-optimization purpose and concrete actions but omits an explicit 'Use when' trigger clause, capping completeness at 3, and relies on a narrow, repetitive set of trigger terms. It is written in appropriate second-person imperative voice and is reasonably distinct from sibling skills.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers like 'when the user asks to write or improve a PR description, summarize a diff for review, or reduce PR size'.

Broaden trigger terms with synonyms users actually say ('pull request', 'PR', 'diff summary', 'code review checklist', 'reviewer notes') to improve keyword coverage.

Tighten the action list to more specific concrete tasks (e.g. 'generate PR descriptions from git diffs, produce reviewer checklists, flag breaking changes') to lift specificity from 4 to 5.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Generate comprehensive PR descriptions, automate review processes, and ensure PRs follow best practices for clarity, size, and reviewability'), but they are pitched at a high level rather than enumerating specific concrete tasks.	4 / 5
Completeness	Clearly states what the skill does, but provides no explicit 'Use when...' trigger clause, which the rubric caps at 3.	3 / 5
Trigger Term Quality	Contains relevant domain terms ('pull requests', 'PR descriptions', 'code reviews', 'reviewability') but lacks synonyms and file/extension-style natural phrasing users would say, and repeats 'PR' heavily without varied trigger language.	3 / 5
Distinctiveness Conflict Risk	Focused on PR optimization/reviewability, a reasonably distinct niche with only minor overlap risk against general code-review skills.	4 / 5
	Total	14 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/comprehensive-review-pr-enhance/SKILL.md
Commit: 3eff4af

Reviewed: 1 day 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.