Content
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill covers the PR creation workflow but is significantly bloated with content Claude already knows (CLI installation, basic gh commands, what conventional commits are). The core workflow has gaps—particularly around how to actually populate the PR template rather than just passing the raw template file. The redundancy between sections (template usage explained twice, best practices and common mistakes overlap) further inflates token cost without adding value.
Suggestions
Remove the Prerequisites section (gh installation and auth) and the 'Additional GitHub CLI PR Commands' section—Claude already knows these commands and can look them up if needed.
Show a concrete, filled-in example of a PR description using the template structure, rather than just referencing the template file. The --body-file approach with a raw template doesn't produce a useful PR.
Consolidate 'Best Practices' and 'Common Mistakes to Avoid' into a single concise section, eliminating the redundancy between them.
Add a post-creation validation step (e.g., 'Verify with `gh pr view` that the PR was created correctly and the description renders properly').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Significant verbosity throughout. Explains how to install gh CLI (Claude knows this), includes a redundant 'Using Templates for PR Creation' section that repeats earlier content, explains basic git concepts, and the 'Additional GitHub CLI PR Commands' section lists common commands Claude already knows. The 'Common Mistakes to Avoid' section largely restates the Best Practices section. | 1 / 3 |
Actionability | Provides concrete bash commands and examples of PR title formats, which is good. However, the PR description creation is incomplete—it references a template file (@.github/pull_request_template.md) but never shows its contents, so Claude can't actually fill it out. The --body-file approach just passes the raw template without filling it in, which isn't correct usage. | 2 / 3 |
Workflow Clarity | The workflow has a reasonable sequence (pre-flight checks → prepare description → create PR), and the pre-flight check for uncommitted changes is a good validation step. However, there's no validation after PR creation (e.g., verify the PR was created successfully, check the PR URL), and the relationship between using --body vs --body-file is unclear—using --body-file with the raw template file doesn't make sense as a workflow step. | 2 / 3 |
Progressive Disclosure | References the PR template file appropriately, but inline content is bloated with sections that could be omitted or separated (installation instructions, additional CLI commands). The 'Using Templates for PR Creation' section at the end is redundant with earlier content. No bundle files are provided despite references to .github/pull_request_template.md. | 2 / 3 |
Total | 7 / 12 Passed |