arquitetura-revisor

Analyze Go, Java, or Python project architecture against the proposta-arq pattern and generate a Markdown report.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/joleques/northstar-ai --skill arquitetura-revisor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arquitetura-revisor
Source: https://github.com/joleques/northstar-ai/tree/main/.codex/skills/arquitetura-revisor
Command: npx skills add https://github.com/joleques/northstar-ai --skill arquitetura-revisor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates inspection of a codebase to detect violations of the proposta-arq architecture (Clean Architecture + Hexagonal + DDD), surfacing structural issues, improper dependencies, and misplaced logic so teams can fix architectural debt before it becomes critical.

Core Features & Use Cases

  • Structure Validation: Verifies presence and naming of expected layers (domain, use_case, application, infra, shared) and detects files placed in incorrect layers.
  • Dependency Flow Analysis: Ensures unidirectional dependencies (infra → application → use_case → domain) and flags imports that break layer boundaries.
  • Per-Layer Review: Checks responsibilities of Application, Use Case, Domain, Infrastructure, and Shared components and reports violations with recommendations.
  • Use Cases: Pre-merge architecture checks, post-refactor validation, legacy code audits, and preparatory reviews before formal code review.

Quick Start

Run an architecture review on the project root, specify the primary language and changed files, and request a Markdown compliance report.

Frequently Asked Questions about arquitetura-revisor

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

FAQPage Schema
How do I automate architecture review for Clean Architecture and DDD violations in a Go project?

Architecture review validates layer separation and dependency direction in Java, Go, and Python monorepos against Clean Architecture, Hexagonal, and DDD patterns. It requires project root access, the primary language, changed files, and test results to generate a Markdown compliance report.

What is the best way to validate unidirectional dependency flow in a hexagonal architecture?

Validating unidirectional dependency flow involves analyzing imports to ensure they follow the infra to application to use_case to domain direction. This dependency analysis flags imports breaking layer boundaries and outputs a per-layer status report with remediation suggestions.

Can I run a pre-merge code review to check domain layer responsibilities in Python?

Pre-merge architecture checks validate layer responsibilities in Python projects by analyzing changed files against expected Clean Architecture and DDD patterns. The review produces a Markdown compliance report summarizing per-layer status, structural violations, and remediation suggestions.

Does this architecture compliance check work with Java monorepos and legacy code audits?

Architecture compliance checks apply to Java monorepos for legacy code audits and post-refactor validation. The review verifies presence and naming of expected layers, detects misplaced files, and outputs a Markdown report summarizing per-layer status and remediation suggestions.

What limitations exist when scanning for DDD structural issues across multiple services?

Scanning for DDD structural issues requires access to the project root, primary language specification, changed files, and test results. It targets specific services or monorepos in Go, Java, or Python, focusing on layer separation and dependency direction to produce a Markdown compliance report.