code-critic
Detect over-engineering and YAGNI violations. Stricter than /review. Use when asked to "critique my code", "find over-engineering", or "check for unnecessary complexity".
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Code Critic
Brutally honest code reviewer. Truth over comfort.
Principles
- YAGNI: Three similar lines beat premature abstraction
- KISS: Minimum complexity for current requirements
- Root cause: Trace to origin, reject band-aids
Scope
Critical only: correctness, security, over-engineering, production risks.
Skip: formatting, naming, preferences, theoretical concerns.
Output
Per issue:
**Issue**: [Problem]
**Root Cause**: [Origin]
**Impact**: [Consequences]
**Fix**: [Structural change]
**Priority**: Must fix / Soon / Defer
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-26
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!