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.
An exemplary dispatcher body: minimal, unambiguous routing logic with a fully specified fallback, and a clean one-level-deep reference structure verified against the actual bundle. The only gaps are the dangling `$REST` variable and the absence of any validation checkpoint for the consequential commit/PR operations.
Suggestions
State how `$REST` is used (e.g., 'pass `$REST` to the chosen action's instructions') so the defined variable is not dangling.
Add a brief pre-flight check for the outward-facing actions (e.g., confirm target branch/repo before committing or opening a PR, or note that each reference file contains its own validation steps) to strengthen workflow checkpoints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 11-line body is lean and assumes Claude's competence: no background concepts, no padding, just dispatch rules ("Treat the first word passed by the user as `$ACTION`, remainder as `$REST`") and three one-line action links. Every token earns its place. | 5 / 5 |
Actionability | Dispatch guidance is concrete and executable ("If `$ACTION` matches one of the actions, follow its instructions"; fallback "choose the action from user intent when clear. Otherwise list the available actions"), and each action links to real reference files with operational detail. It falls short of fully-executable anchor 5 because `$REST` is defined but never explained or used in the body, leaving a minor gap in how it reaches the sub-instructions. | 4 / 5 |
Workflow Clarity | The decision sequence is clear and covers all input cases (match, empty, non-match with explicit fallback behavior), matching the clear-sequence anchor. It is not anchor 5 because the body has no validation or verification checkpoints for the consequential operations it dispatches to (commits and PR creation are outward-facing), though the operation details live in the references rather than the body. | 4 / 5 |
Progressive Disclosure | The body is a clean overview dispatching to three clearly signaled, one-level-deep references ([commit](references/commit.md), [pr](references/pr.md), [review](references/review.md)), each with a one-line summary; all three files exist, contain real standalone content, and contain no nested references, matching the well-signaled one-level-deep anchor exactly. | 5 / 5 |
Total | 18 / 20 Passed |