oo-review

To review object-oriented code in a PR diff, the skill identifies applied patterns like Gang of Four or DDD, evaluates their implementation quality, and provides severity-labeled findings with file:line references. It also explains unfamiliar patterns pedagogically.

Checking DDD and clean architecture application involves routing deep domain modeling questions to specialized subagents that recognize pattern lineages against authoritative rules, differentiating between blockers, design issues, and educational notes.

Yes, you can review code changes using file paths or git ranges. The skill supports path-based surveys and excludes generated, lockfile, or irrelevant content automatically, allowing targeted deep dives into specific areas of your codebase.

Object-oriented pattern recognition works by naming the likely OO lineage in play, such as hexagonal or onion architectures, and briefly explaining the concepts when they are unfamiliar, helping you understand the code and consider better alternatives.

When reviewing OO code, findings are tagged by severity as blocker, major, minor, or nit. Separate pedagogical-note entries are also produced alongside these actionable findings to provide educational context for the identified design issues.

To get architecture critique and OO design guidance, review your changes against the main branch and request deep dives. The skill routes complex architecture and pattern questions to specialist subagents for targeted, expert evaluation.