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.
The body is a lean, actionable set of pytest testing rules with concrete commands, named patterns, per-step completion criteria, and a final self-check checklist. It assumes Claude's competence throughout and organizes content into clear sections with one-level-deep external references.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body assumes Claude knows pytest and mocking, with every line giving actionable rules or commands and no padding explaining what tests or libraries are, matching the lean-and-efficient 5 anchor. | 5 / 5 |
Actionability | Concrete commands ("uv run pytest dimos/path/to/test_file.py -k test_name", "./bin/pytest-fast") and named patterns ("mocker.patch.object", "assert_called_once_with", "tmp_path") are executable, but the mocking guidance is described as a pattern rather than a full copy-paste code block, a minor gap. | 4 / 5 |
Workflow Clarity | Five numbered steps each carry a "Completion:" checkpoint, plus a Validation section and a Final self-check checklist; an explicit fail→fix→re-run feedback loop is implied rather than spelled out, keeping it just below the 5 anchor. | 4 / 5 |
Progressive Disclosure | Sections (Steps, Test shape, Fixtures, Assertions, Mocking, Global state, Validation, Final self-check) are well organized, and the external doc references are one level deep and clearly signaled with "Consult these only when the branch needs more context"; with no bundle files this is well-structured but not the ideal split-overview 5. | 4 / 5 |
Total | 17 / 20 Passed |