code-critic

Quick Review

The skill provides a clear philosophical framework for strict code review focused on YAGNI/over-engineering, with well-defined principles and output format. However, the description is quite brief and doesn't fully specify invocation parameters (e.g., which files/code to review, how to invoke). Task knowledge is moderate—it defines what to look for and output structure, but lacks concrete examples, heuristics for detecting over-engineering, or decision criteria. Structure is good: concise, well-organized for a focused skill. Novelty is moderate; while the strict YAGNI lens is somewhat differentiated from generic review, a CLI agent could approximate this with detailed prompting, though this skill does provide a reusable template and saves tokens on repeated invocations.