Content
72%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.
The body is exemplary in its token efficiency — it locates the authoritative version in source rather than hardcoding it, and states the bump policy and goal in four lines. Its weakness is executability: it never says how to find version references in the docs or how to confirm none were missed, leaving the core task underspecified.
Suggestions
Add the derivation rule explicitly ("next = current with the patch segment incremented") so the bump arithmetic is unambiguous.
Add a concrete discovery step, e.g. `grep -rn "<current version>" docs/` or the doc paths where the version is rendered, instead of the bare imperative "Ensure the docs correctly reference the next version".
Close with a verification step such as re-running the search to confirm no stale version strings remain — required because a doc-wide update is a batch operation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Four lean lines with zero padding and no explanation of concepts Claude already knows; the time-sensitive version value is resolved via a live file pointer (`packages/core/src/version.ts`) rather than a hardcoded number, so nothing will go stale. Every line either locates the version source, states the bump type, or defines the task. | 5 / 5 |
Actionability | The file path is a concrete, readable pointer, but "Ensure the docs correctly reference the next version" is a goal rather than an instruction — no search strategy (which docs, grep for what), no doc locations, and no arithmetic for deriving the next patch version from the current one. | 3 / 5 |
Workflow Clarity | An implicit read-current → derive-next-patch → update-docs sequence exists, but updating docs across a repo is a batch operation with no verification step (e.g. grep for leftover old-version strings), which caps workflow clarity at 3 per the batch-operations rule. | 3 / 5 |
Progressive Disclosure | A four-line, single-file body with no bundle files needs no external references or sections; it is trivially navigable and nothing that belongs in a separate file is inlined, satisfying the simple-skill exception. | 5 / 5 |
Total | 16 / 20 Passed |