Content
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a verbose, textbook-style document that explains well-known software engineering concepts Claude already understands, rather than providing lean, actionable instructions for performing code reviews. It lacks a clear sequential workflow, has no validation checkpoints, and dumps all content into a single monolithic file. The MCP tool integration section adds some value but uses non-executable pseudo-code.
Suggestions
Remove all explanations of concepts Claude already knows (SOLID, DRY, SQL injection patterns, N+1 queries, dependency injection) and replace with a concise checklist of what to check during review.
Add a clear sequential workflow: 1) Receive review target, 2) Run automated checks, 3) Perform manual review by category, 4) Validate findings, 5) Format and report results — with explicit validation steps.
Extract the review feedback template and MCP integration examples into separate reference files, keeping SKILL.md as a lean overview with pointers.
Make the MCP tool calls executable with correct syntax rather than pseudo-JavaScript, and clarify the exact entry point — what does the agent do first when invoked?
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~250+ lines. Explains basic concepts Claude already knows (SOLID principles, DRY, SQL injection, N+1 queries, dependency injection). The security checklist, performance checks, and code quality examples are all textbook knowledge that wastes token budget. The review guidelines section ('Be Constructive', 'Focus on the code, not the person') is generic advice Claude doesn't need. | 1 / 3 |
Actionability | Provides concrete code examples for common issues (SQL injection, N+1 queries, naming), and a review feedback template is useful. However, much of it is illustrative rather than executable — the MCP tool integration examples use pseudo-JavaScript that isn't directly executable, and the skill doesn't give clear instructions on what to actually do when invoked (e.g., which files to review, how to start). | 2 / 3 |
Workflow Clarity | There is no clear sequential workflow for performing a review. The numbered sections (1-5) are categories of review, not steps in a process. There are no validation checkpoints, no feedback loops for when issues are found, and no clear entry/exit criteria. The 'Automated Checks' section lists commands but doesn't integrate them into a workflow with verification steps. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files and no content splitting. Everything — from basic examples to MCP integration to review templates — is crammed into a single file. The extensive code examples for well-known patterns (SQL injection, DRY, SOLID) should either be omitted or placed in a reference file. | 1 / 3 |
Total | 5 / 12 Passed |