hexagonal-review

Evaluate code for hexagonal architecture compliance across ports, adapters, and layer boundaries.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/canopy-network/launchpad --skill hexagonal-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hexagonal-review
Source: https://github.com/canopy-network/launchpad/tree/main/.claude/skills/hexagonal-review
Command: npx skills add https://github.com/canopy-network/launchpad --skill hexagonal-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers assess hexagonal architecture compliance, ensuring core domain logic stays decoupled from external systems, and that ports and adapters are correctly defined and implemented.

Core Features & Use Cases

  • Port & Adapter Checklist: Validate the design of ports (interfaces) and adapters (implementations) to ensure correct boundaries.
  • Architecture Boundaries: Assess the layering (Domain/Core, Ports, Adapters, Infrastructure) for proper separation and testability.
  • Use Case: When reviewing a new feature, verify that core business rules are isolated from frameworks, and that adapters can be swapped without changing core logic.

Quick Start

Review the project's ports and adapters for the new payment feature and generate a list of suggested improvements.

Frequently Asked Questions about hexagonal-review

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

FAQPage Schema
How do I review code for hexagonal architecture compliance?

Hexagonal architecture review assesses whether ports are abstract interfaces, adapters are swappable implementations, and core domain logic remains isolated from frameworks and I/O code. Evaluate layer boundaries—Domain/Core, Ports, Adapters, Infrastructure—to ensure separation of concerns and testability across your codebase.

What are ports and adapters in hexagonal architecture?

Ports are abstract interfaces that define how external systems interact with core domain logic. Adapters implement those interfaces to connect specific frameworks, databases, or APIs. Together they decouple business rules from external dependencies, allowing adapters to be swapped without changing core logic.

How do I identify when my code violates hexagonal architecture boundaries?

Violations occur when framework code or I/O operations leak into core domain logic, ports lack abstraction, or adapters cannot be replaced independently. Review checklist artifacts flag these issues: framework dependencies in domain code, concrete implementations in port interfaces, or adapters tightly coupled to infrastructure details.

Can I apply hexagonal architecture review during code generation and quality gates?

Yes. Integrate architecture compliance checks into code generation pipelines and quality gates to assess port abstraction, adapter isolation, and layer separation continuously. This ensures new features maintain core domain decoupling and produces reference structures and checklists for ongoing validation.

What's the benefit of keeping core domain free from framework code?

Isolating core domain from frameworks enables independent testing of business logic, simplifies maintenance, and allows framework or database changes without rewriting core rules. Hexagonal architecture review verifies this isolation, ensuring adapters handle all external system concerns while domain code focuses purely on business logic.