review▌

Automated code review and refactoring against project-specific coding guidelines and instructions. \n \n Reads coding standards from .github/instructions/*.md and .github/copilot-instructions.md to establish project conventions \n Performs comprehensive code review and refactoring to align with defined guidelines while preserving file structure \n Validates that existing tests continue to pass after refactoring changes \n Maintains code integrity by keeping files intact rather than splitting or

Comprehensive C#/.NET design pattern analysis with actionable improvement recommendations. \n \n Evaluates six core patterns: Command, Factory, Dependency Injection, Repository, Provider, and Resource patterns against GoF and SOLID principles \n Analyzes architecture compliance including namespace conventions, project separation, async/await patterns, and structured logging implementation \n Reviews code quality across security, testability, maintainability, and performance dimensions with speci

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

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.

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: