Content
82%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 highly actionable, well-structured procedural skill with concrete commands and clear sequencing for both creating and editing PRs. The main improvement areas are removing the duplicated body-quoting warning and adding an explicit post-creation validation step.
Suggestions
Consolidate the repeated "do not use --body, shell quoting mangles backticks" warning into a single note referenced from both the editing and creating sections.
Add an explicit validation step after `gh pr create` (e.g. confirm the PR opened via `gh pr view`) before instructing the user to verify the deploy preview.
Consider moving the 10 title examples and the three summary examples into a references/ file to keep the core workflow lean while preserving them as lookup material.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient and consists of repo-specific conventions Claude would not already know, but the `--body` quoting warning is repeated across the editing and creating sections and a few explanatory asides (e.g. "this is intentional") could be trimmed. | 4 / 5 |
Actionability | Concrete, copy-paste-ready commands appear throughout (e.g. `gh pr view <number> --json title,body`, `gh pr create --base production --draft --title "..." --body-file /tmp/pr-body.md`) with exact file paths and explicit tool usage covering the common cases. | 5 / 5 |
Workflow Clarity | Steps 1–4 for creating a PR are clearly sequenced with checkpoints (asking about untracked files, reading the template fresh) and the "After pushing" section provides a sync feedback loop, but there is no explicit validation that the PR was created successfully before sharing the URL. | 4 / 5 |
Progressive Disclosure | No bundle files exist; the single SKILL.md is well organized with clear section headers and reads the live PR template from disk rather than hardcoding it. Minor gaps: the long title-example and summary-example blocks could optionally live in a reference file. | 4 / 5 |
Total | 17 / 20 Passed |