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

80%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/gh-pull-request/SKILL.md

Quality

Content

77%

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

This is a strong, highly actionable skill with clear workflow sequencing and explicit validation checkpoints throughout. Its main weakness is verbosity in the FQCN section, which includes extensive explanation of edge cases and failure diagnostics that could be condensed or moved to a supplementary file. Overall it serves its purpose well as a concrete, project-specific PR workflow guide.

Suggestions

Extract the FQCN audit details (acceptable exceptions, failure diagnostics, ripgrep pattern) into a separate FQCN_CHECK.md reference file to reduce the main skill's token footprint.

Condense the FQCN section's prose — the explanation of what checkstyle misses and the 'Range [0, -1)' diagnostic could be shortened to bullet points rather than full paragraphs.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient and project-specific, but the FQCN section is quite verbose with extensive explanation of edge cases and failure modes that could be tightened. The license header and commit sections are lean.	2 / 3
Actionability	Provides fully executable bash commands, specific ripgrep patterns, exact PR template formats with checkboxes, and concrete gh CLI commands. Every step is copy-paste ready with real project-specific details.	3 / 3
Workflow Clarity	Clear sequential workflow: pre-flight checks (compile → license → FQCN audit) → commit/push → PR creation. Includes explicit validation/feedback loops (fix license headers and re-check, re-run checkstyle after FQCN fixes, check for cryptic error patterns). Branch safety guardrail is explicit.	3 / 3
Progressive Disclosure	Content is well-structured with clear headers and logical sections, but the FQCN audit section is quite long and could be split into a separate reference file. The PR template examples inline are borderline — useful but add bulk. No bundle files exist to offload detail to.	2 / 3
	Total	10 / 12 Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong description that clearly articulates specific capabilities around PR branch management with pre-flight verification. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The specificity of the pre-flight checks (compile, checkstyle, license headers) and the PR creation fallback make it highly distinctive.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to commit and push code changes, submit a PR, or run pre-commit checks like compile, checkstyle, or license verification.'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: verify, commit, push changes, run pre-flight checks (compile, checkstyle, license headers), create PR. These are all concrete, actionable operations.	3 / 3
Completeness	Clearly answers 'what does this do' with specific actions (verify, commit, push, run checks, create PR), but lacks an explicit 'Use when...' clause. The 'when' is only implied by the nature of the actions described.	2 / 3
Trigger Term Quality	Includes natural keywords users would say: 'commit', 'push', 'PR', 'branch', 'compile', 'checkstyle', 'license headers', 'pre-flight checks'. These are terms developers naturally use when working with pull requests and code submission workflows.	3 / 3
Distinctiveness Conflict Risk	Clearly distinct niche combining PR workflow with pre-flight checks (compile, checkstyle, license headers). The combination of commit/push with specific verification steps makes it unlikely to conflict with generic git or CI skills.	3 / 3
	Total	11 / 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: apache/skywalking
Commit: bf0fe4b

Reviewed: 24 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.