gh-pull-request

Verify, commit, and push changes on a PR branch. Runs pre-flight checks (compile, checkstyle, license headers) before every push. Also creates the PR if one doesn't exist yet.

Quality

83%

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

Quality

Content

92%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 highly actionable and well-sequenced with strong validation checkpoints for the destructive post-merge branch deletion. Only minor conciseness trims are warranted; progressive disclosure is appropriate for a self-contained workflow skill.

Dimension	Reasoning	Score
Conciseness	Mostly lean and command-driven with a few sections (the FQDN exceptions list and the repeated squash-merge -d/-D explanation) that could be trimmed slightly.	4 / 5
Actionability	Fully executable throughout — concrete ./mvnw, license-eye, ripgrep, git, and gh commands with a ready heredoc PR-create snippet cover the common cases copy-paste ready.	5 / 5
Workflow Clarity	Clear numbered sequences for pre-flight checks and post-merge cleanup with explicit validation/feedback loops (re-run checkstyle after fix, confirm content landed in master before force-delete, 'Do NOT skip step 3').	5 / 5
Progressive Disclosure	Single self-contained, well-sectioned SKILL.md with no nested references and no bundle files needed; organization is clear and one-level-deep.	5 / 5
	Total	19 / 20 Passed

Description

75%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 is specific and distinctive, clearly conveying a PR-branch workflow with concrete pre-flight checks. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness at 3.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when committing and pushing changes on a PR branch or when the user asks to create/open a PR.'

Include the spelled-out term 'pull request' alongside 'PR' to broaden natural trigger coverage.

Mention the target project context (e.g. SkyWalking/maven) in the description to sharpen distinctiveness further.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — verify/commit/push, pre-flight checks (compile, checkstyle, license headers), and PR creation — with comprehensive coverage of its PR-branch domain.	5 / 5
Completeness	Has a clear, multi-part 'what' but no explicit 'Use when...' trigger clause, so 'when' is only weakly implied; the missing-trigger-guidance cap applies.	3 / 5
Trigger Term Quality	Good natural keyword coverage ('commit', 'push', 'PR', 'checkstyle', 'license headers') but a few common synonyms (e.g. 'pull request' spelled out) are missing.	4 / 5
Distinctiveness Conflict Risk	Narrow, specific niche (PR-branch workflow with maven/checkstyle/license-eye pre-flight and optional PR creation) with distinct triggers and minimal overlap risk.	5 / 5
	Total	17 / 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: apache/skywalking
Path: .claude/skills/gh-pull-request/SKILL.md
Commit: 521b2ab

Reviewed: 5 days 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.