create-pr

Full PR creation pipeline — self-review, code review checks, and PR creation with a structured template.

Quality

58%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./devflow-plugin/skills/create-pr/SKILL.md

Quality

Content

85%

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

This is a well-structured PR creation skill with strong actionability and clear workflow sequencing including validation gates and user approval checkpoints. The executable commands and PR template are concrete and ready to use. Minor conciseness improvements could be made by trimming the self-review checklist (Claude already knows these patterns) and tightening introductory text.

Suggestions

Trim or remove the self-review checklist in step 2 — Claude already knows what to look for in code review; a brief 'Self-review the diff for issues' suffices.

Remove the opening sentence 'You are creating a pull request. This command runs the full PR pipeline.' as it restates what the skill description already conveys.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but has some unnecessary verbosity. The self-review checklist items are things Claude already knows to check, and phrases like 'You are creating a pull request. This command runs the full PR pipeline.' are somewhat redundant. However, the overall structure is reasonably tight.	2 / 3
Actionability	Provides fully executable commands throughout — git log/diff, devflow check, yarn lint/build/test, gh pr create with a complete heredoc template. The PR body template is copy-paste ready with clear placeholders.	3 / 3
Workflow Clarity	Clear 8-step sequence with explicit validation checkpoints: self-review at step 2, automated checks at step 3, a decision gate at step 4 (report issues and ask user), user approval at step 6, and a constraint to never create PRs with failing checks. The feedback loop for error recovery is well-defined.	3 / 3
Progressive Disclosure	For a skill of this size (~70 lines) with no need for external references, the content is well-organized with clear sections (Steps, Important) and numbered workflow. No bundle files are needed and none are referenced, which is appropriate.	3 / 3
	Total	11 / 12 Passed

Description

32%

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 communicates the general purpose of the skill — a PR creation pipeline — but lacks explicit trigger guidance ('Use when...') and misses common keyword variations like 'pull request'. It is moderately specific but would benefit from more concrete action descriptions and clearer disambiguation from related code review or git workflow skills.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to create a pull request, open a PR, or submit changes for review.'

Include common keyword variations such as 'pull request', 'open PR', 'merge request', 'PR description', and 'GitHub/GitLab PR' to improve trigger term coverage.

Specify the concrete actions more clearly, e.g., 'Runs linting and test checks, generates a self-review summary, and creates a pull request with a structured description template including summary, changes, and testing sections.'

Dimension	Reasoning	Score
Specificity	Names the domain (PR creation) and some actions (self-review, code review checks, PR creation with structured template), but these are somewhat high-level and not deeply concrete — e.g., what does 'self-review' entail specifically? What 'code review checks'?	2 / 3
Completeness	Describes what the skill does (PR creation pipeline with self-review and code review checks) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'when' is entirely absent, warranting a 1.	1 / 3
Trigger Term Quality	Includes 'PR creation' and 'code review' which are natural terms users might say, but misses common variations like 'pull request', 'open a PR', 'submit PR', 'GitHub PR', 'merge request', or 'PR description'.	2 / 3
Distinctiveness Conflict Risk	The combination of PR creation + self-review + structured template is somewhat distinctive, but 'code review checks' could overlap with a general code review skill, and 'PR creation' without specifying the platform (GitHub, GitLab, etc.) leaves room for conflict.	2 / 3
	Total	7 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: AndreJorgeLopes/devflow
Commit: 8d872bf

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.