Content
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is well-organized, lean, and highly actionable: a complete template, required-field table, good/bad examples, skip-label guidance, and a validation checkpoint all in roughly 70 lines with one-level-deep references. It assumes Claude's competence and leaves depth to external pointers.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean and dense: file-format table, required-field constraints, and a runnable validate command appear with no padding or explanation of concepts Claude already knows. Every line earns its place. | 3 / 3 |
Actionability | Provides a complete frontmatter template, a field-by-field table with required/optional flags, good/bad body examples, exempted path globs, and a copy-paste validate command (`pnpm run release:notes:validate`). | 3 / 3 |
Workflow Clarity | Sequences the full workflow — choose file name, fill frontmatter, write body, decide on no-release-note skip, then verify — and closes with an explicit validation command/checkpoint before finishing. | 3 / 3 |
Progressive Disclosure | Keeps the body as a concise overview and pushes the full format reference and gate policy to clearly signaled one-level-deep pointers (`.changes/README.md`, `tools/release/check-release-note-gate.mjs`); no bundle files exist to over-fragment. | 3 / 3 |
Total | 12 / 12 Passed |