Content
86%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A tight, well-sequenced instruction skill: concrete git commands, a specific PR body template with exact section formats, and clear tone guidance, with no filler. The remaining gaps are a shown-but-not-spelled-out gh pr create invocation and the absence of error-recovery guidance around push and PR creation.
Suggestions
Show the actual gh pr create invocation (e.g., gh pr create --title "$TITLE" --body "$(cat <<'EOF' ... EOF)") so the final step is copy-paste ready like the git commands.
Add brief error-recovery guidance for the push/create phase (e.g., what to do if the push is rejected or gh is unauthenticated) to close the validation gaps.
Remove the line-11 restatement of the frontmatter description, which duplicates content already implied by the title.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and presumes Claude's competence ("Assume they know how to run the project"); every section gives novel, task-specific guidance rather than concepts Claude already knows. The only trimmable token is line 11, which restates the description verbatim — insufficient to drop below anchor 5. | 5 / 5 |
Actionability | Most steps give exact, executable commands (git status, git log/diff main..HEAD, git rev-parse, git push -u origin HEAD) plus a concrete <details> body template and title constraints (under 72 chars, imperative mood). However, the final gh step is described ("Create the PR using gh pr create... Use a HEREDOC") rather than shown as a copy-paste-ready invocation, a minor gap that keeps it at anchor 4 instead of 5. | 4 / 5 |
Workflow Clarity | A clear five-step sequence with interactive checkpoints (rebase check, uncommitted-changes handling, pushed-branch check). There are no explicit error-recovery or validation steps for the risky final phase (push failure, gh authentication errors, PR creation failure), so it matches anchor 4 (minor validation gaps) rather than anchor 5's explicit feedback loops. The destructive/batch cap does not apply since PR creation is neither destructive nor batch. | 4 / 5 |
Progressive Disclosure | A single, well-sectioned file (~80 lines) with no bundle references. Splitting this cohesive single workflow into external reference files would add navigation cost without benefit, so per the under-50-lines/no-external-references guidance the well-organized section structure merits a 5. | 5 / 5 |
Total | 18 / 20 Passed |