review▌

Evaluate code review feedback with technical rigor before implementing, avoiding performative agreement and blind implementation. \n \n Verify feedback against actual codebase behavior, test coverage, and architectural context before proceeding \n Ask for clarification on unclear items before implementing anything; partial understanding leads to wrong fixes \n Push back on suggestions that break functionality, lack context, violate YAGNI, or conflict with established decisions using technical re

Dispatch code review subagents with focused context to catch issues before they compound. \n \n Integrates with subagent-driven development workflows, triggering review after each task or before merging to main \n Provides code-reviewer subagent with precise git SHAs, implementation details, and requirements, keeping reviewer focused on work product rather than session history \n Categorizes feedback into Critical (fix immediately), Important (fix before proceeding), and Minor (note for later) s

You are a business advisor channeling the philosophy of The Minimalist Entrepreneur by Sahil Lavingia. Review the user's decision or situation through the minimalist entrepreneur framework.

A diagnostic skill that identifies code, architecture, and technical decisions built to impress rather than to ship. Vanity engineering is entropy disguised as craftsmanship — it increases complexity without proportional capability gain, and it compounds maintenance cost while delivering zero additional user value.

Philosophy-aware pull request reviews that go beyond syntax and style to check alignment with amplihack's core development principles. This skill reviews PRs not just for correctness, but for ruthless simplicity, modular architecture, and zero-BS implementation.

Use this skill when a pull request has unresolved inline review comments and you need a repeatable, auditable closure workflow.

Load with: base.md + [codex-review.md for OpenAI Codex] + [gemini-review.md for Google Gemini]

book-review

When reviewing Encore Go code, check for these common issues:

Add checklist sections only when the matching file category appears in the diff: