Content
93%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 an exemplary conventions skill: terse, entirely repo-specific, and immediately actionable, with an explicit fix-then-stage feedback loop for the pre-commit gate. Its only weakness is that multi-step flows are scattered across sections without a consolidated end-to-end sequence and with limited guidance on recovering from a failing commit-msg hook.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line carries repo-specific facts Claude could not know (e.g. '`exactOptionalPropertyTypes` is on', hooks 'skip when `CI=true`', 'format is checked, not fixed') with zero padding or explanation of known concepts, matching the lean-and-efficient anchor 5. | 5 / 5 |
Actionability | Copy-paste-ready commands (`bun run verify`, `bun run fmt:check`, `bun run ci`) with exact script paths (`scripts/check-commit-subject.ts`, `scripts/certs.ts`, `scripts/serve-https.ts`) and explicit do/don't rules covering the common cases, matching the fully-executable anchor 5. | 5 / 5 |
Workflow Clarity | The commit workflow is well sequenced with an explicit feedback loop ('format is checked, not fixed — run `bun run fmt` / `md:fmt`, then stage') and hook installation behavior is documented, but workflows are distributed across sections rather than one explicit end-to-end sequence and error recovery beyond 'never bypass hooks' is thin, matching anchor 4. | 4 / 5 |
Progressive Disclosure | A compact, well-sectioned overview with detail appropriately pushed out ('Details in docs/local-https.md', repos listed in `repos.json`) and nothing inlined that belongs in a separate file, matching the clear-overview anchor 5 for a single-file bundle. | 5 / 5 |
Total | 19 / 20 Passed |