audit

Checks .NET projects for hexagonal architecture and validates layer dependencies and contracts.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/lcmassena/AI_Skills --skill audit-lcmassena
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/lcmassena/AI_Skills/tree/main/hexagonal-architect/audit
Command: npx skills add https://github.com/lcmassena/AI_Skills --skill audit-lcmassena

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auditors often struggle to verify that a .NET solution adheres to hexagonal architecture, with correct layer boundaries and patterns across multiple modules.

Core Features & Use Cases

  • Layer dependency validation: ensures Functions, Application, Domain, Shared, and Adapters layers reference only allowed layers.
  • MediatR and pattern compliance: confirms presence of Shared abstractions, domain events, and correct handler interfaces.
  • Architecture health checks: identifies drift, missing ports, and potential violations across the codebase.

Quick Start

Install and run the audit against your solution to generate a comprehensive architecture conformance report.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I verify hexagonal architecture conformance in a .NET solution?

To verify hexagonal architecture conformance in a .NET solution, run an audit against the codebase to validate layer boundaries, repository ports, and MediatR abstractions. This generates a comprehensive report identifying missing ports and boundary violations across Functions, Application, Domain, Shared, and Adapters layers.

What does an architecture audit check for in a CQRS and MediatR project?

An architecture audit for CQRS and MediatR projects checks for correct handler interfaces, domain events, and Shared abstractions. It ensures Result-based return types are used correctly and validates that no business logic leaks into adapters or infrastructure, maintaining strict layer dependency compliance.

Can I use this audit tool on any .NET solution or do I need specific patterns?

You need specific patterns to use this audit tool effectively. It is applied to .NET solutions implementing hexagonal architecture with CQRS and MediatR patterns, requiring distinct Functions, Application, Domain, Shared, and Adapters layers to accurately validate dependencies and conformance.

How do I identify architecture drift and missing ports in my domain-driven design?

To identify architecture drift and missing ports in domain-driven design, execute an architecture health check across your codebase. This detects potential violations and confirms the presence of required repository ports and MediatR abstractions, ensuring layer boundaries remain strictly enforced.

What is the best way to prevent business logic from leaking into infrastructure adapters?

The best way to prevent business logic from leaking into infrastructure adapters is to perform automated layer dependency validation. This verifies that adapters reference only allowed layers and confirms that Result-based return types and domain events are correctly implemented within the application core.