Content
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A tight, highly actionable PR-writing guide that assumes Claude's competence and supplies concrete templates, examples, and section rules. Its only gap is workflow clarity: the procedure is sequenced in prose with a CI warning rather than an explicit numbered validate-and-retry loop.
Suggestions
Convert the body-building procedure into a short numbered list (read template → fill sections → delete unused sections/placeholder text → remove the preamble line → verify CI passes) so the sequence and its checkpoint are explicit.
Add a brief validation step framed as a feedback loop, e.g. 'After removing the preamble line, confirm the pr-validation.yml check will pass; if it flags the preamble or empty sections, fix and re-check before opening the PR.'
State the decision point for choosing Option A vs Option B as an explicit checkpoint (e.g., 'pick one based on whether the change has a meaningful scope') so the title step is unambiguous.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is focused and assumes Claude's competence — it gives title style, a body template procedure, and section notes with no concept-explanation padding (e.g., it never explains what a PR is). Every section earns its place, including the example lists which serve actionability rather than verbosity. | 3 / 3 |
Actionability | Fully concrete guidance: code-block title templates with six and three real examples, exact section names (## Description, ## Breaking Changes, ## Reviewer Guidance), a specific source file (.github/pull_request_template.md), a named CI check (pr-validation.yml), and the AB#<item-id> work-item format — copy-paste ready. | 3 / 3 |
Workflow Clarity | A sequence is present (read the template, fill in sections, delete non-applicable sections, remove the preamble line) and a CI failure mode is identified, but the steps are prose rather than a numbered sequence and the validation is a warning rather than an explicit validate→fix→retry loop. | 2 / 3 |
Progressive Disclosure | The skill is under 50 lines with no bundle files and is organized under clear headers (# PR Body Template, ## Notes on body sections); it appropriately points to the repo's own pull_request_template.md rather than duplicating it, so the single-level organization is well-handled. | 3 / 3 |
Total | 11 / 12 Passed |