Content
92%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 content is well-structured and highly actionable, with a clear workflow featuring validation checkpoints, concrete code examples, and a well-organized one-level-deep reference system. Its only weakness is a small amount of redundant conceptual listing in the Knowledge Reference line.
Suggestions
Trim the 'Knowledge Reference' line listing SOLID/DRY/KISS/YAGNI etc. — Claude already knows these; keep only any non-obvious project-specific conventions.
The description's 'Invoke for PR reviews, code quality checks, refactoring suggestions, review code, code quality' duplicates terms already covered by the preceding 'Use when' clause; consolidate to reduce redundancy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean with no padding about what code review is, but the 'Knowledge Reference' line listing 'SOLID, DRY, KISS, YAGNI, design patterns, OWASP Top 10, language idioms, testing patterns' restates concepts Claude already knows and could be trimmed. | 4 / 5 |
Actionability | Provides copy-paste-ready bad/good code pairs for N+1 queries, magic numbers, and SQL injection, plus a reference table with load conditions, MUST/MUST NOT constraints, and a 7-section output template — fully executable guidance covering common cases. | 5 / 5 |
Workflow Clarity | A clear 5-step Core Workflow includes an explicit validation checkpoint ('Summarize the PR intent... If you cannot, ask the author to clarify') and a feedback loop ('If critical issues are found in step 3, note them immediately and do not wait until the end'). | 5 / 5 |
Progressive Disclosure | A well-signaled reference table points one level deep to six real files in references/ (verified present) each with a 'Load When' condition, keeping the overview concise while splitting detail appropriately. | 5 / 5 |
Total | 19 / 20 Passed |