interface-layer

This skill audits HTTP delivery and repository implementations against clean architecture principles, enforcing patterns for request parsing, response formatting, dependency inversion, and efficient data access to prevent common integration errors.

Checking SQS message handler setup in a Go application involves auditing the SQS delivery layer for proper lifecycle management and message processing patterns. This validates that your handlers adhere to defined architectural best practices before code integration.

Enforcing dependency inversion in Go repository implementations requires auditing query scoping, error handling, and data access patterns against clean architecture standards. This ensures your repositories correctly abstract data sources and adhere to port-adapter boundaries.

Yes, you can automatically audit Go API endpoints and PostgreSQL repositories before merging by running an interface layer audit. This catches potential bugs related to status codes, parameter binding, and inefficient queries in your internal API and repository directories.

Clean architecture validation works with existing Go internal API directories by analyzing your current HTTP delivery and repository implementations. It evaluates routing, middleware application, and query efficiency without requiring external dependencies to function.

Your Go repository implementation may fail clean architecture boundary checks due to improper dependency inversion, inefficient query scoping, or incorrect error handling. Auditing the interface layer identifies these violations against defined architectural principles and best practices.