Verified:GitHub

code-critic

Flag over-engineering and YAGNI violations in code reviews with per-issue outputs.

Updated Jan 10, 2025

Ready to run

npx skills add https://github.com/hairihou/dotfiles --skill code-critic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-critic
Source: https://github.com/hairihou/dotfiles/tree/main/src/.claude/skills/code-critic
Command: npx skills add https://github.com/hairihou/dotfiles --skill code-critic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It acts as a brutally honest code reviewer, prioritizing correctness, security, and production risk, while avoiding non-actionable concerns.

Core Features & Use Cases

Critical analysis of potential logic flaws, edge cases, security risks.
Root-cause focus: traces issues to origin and resists quick band-aids.
Actionable outputs with a suggested fix and priority.

Quick Start

Request a concise critique of a function that introduces an unnecessary abstraction, with a recommended concrete refactor and high priority.

Frequently Asked Questions about code-critic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I identify over-engineering and unnecessary abstractions in code reviews?▼

Code critique identifies over-engineering by flagging abstractions that violate YAGNI and KISS principles. It traces logic flaws and unnecessary complexity to their root cause, then provides actionable fixes with priority levels, helping you enforce minimality in production code.

What's the best way to conduct critical code reviews focused on correctness and security?▼

Critical code review prioritizes correctness, security, and production risk while excluding formatting or style concerns. This Skill applies structured analysis that captures Problem, Root Cause, Impact, Fix, and Priority for each issue, ensuring reviews stay actionable and focused on real risks.

How do I avoid quick band-aid fixes and address root causes in code review?▼

Root-cause focus traces issues to their origin rather than addressing symptoms. By identifying the underlying problem driving a flaw, you replace superficial patches with concrete, sustainable refactors that eliminate the issue durably.

Can I use code critique to flag logic flaws and edge cases before production?▼

Yes. Code critique applies brutal, honest analysis to detect logic flaws, edge cases, and security risks before deployment. It delivers standardized output with suggested fixes and priority ratings, enabling teams to catch production risks early.

What should I exclude from a critical code review to keep feedback actionable?▼

Critical code review excludes formatting, naming, and stylistic preferences—concerns that don't affect correctness or security. By filtering to functional and security issues only, reviews remain concise and focused on problems that matter in production.