Verified:GitHub

clean-architecture-review

Detect layer boundary violations and dependency-direction leaks with P0-P3 severities.

2|Updated Mar 2, 2026

Search Tags:#architecture #code-review #clean-architecture #solid-principles #dependency-direction #production-robustness

Ready to run

npx skills add https://github.com/tizee/skills --skill clean-architecture-review-tizee

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clean-architecture-review
Source: https://github.com/tizee/skills/tree/main/skills/clean-architecture-review
Command: npx skills add https://github.com/tizee/skills --skill clean-architecture-review-tizee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify architectural violations, cross-layer boundary issues, and design debt that degrade maintainability and reliability.

Core Features & Use Cases

Map architecture and trace dependencies to reveal layer violations and cross-boundary coupling.
Produce prioritized findings with P0-P3 severities and concrete remediation guidance.
Use in PR reviews, legacy audits, and CI gates to enforce architectural quality.

Quick Start

Provide a structured audit of the target codebase to surface boundary violations and produce prioritized, actionable fixes.

Frequently Asked Questions about clean-architecture-review

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

FAQPage Schema

How do I detect clean architecture violations and cross-layer coupling in my codebase?▼

Detect clean architecture violations by auditing the codebase to trace dependencies, reveal layer boundary violations, and identify dependency-direction leaks across domain, application, interface, and infrastructure layers.

What's the best way to enforce SOLID and KISS principles during a PR review?▼

Enforce SOLID and KISS principles during PR reviews by running an architectural audit that identifies design debt and produces prioritized findings with concrete remediation guidance to prevent violations from merging.

Can I use automated architecture checks as CI gates to prevent production risks?▼

You can use automated architecture checks as CI gates to intercept cross-layer boundary issues and production risks before deployment, ensuring maintainability and reliability across your domain and infrastructure boundaries.

How do I audit a legacy codebase for dependency-direction leaks and architectural debt?▼

Audit a legacy codebase by mapping its architecture and tracing dependencies to surface cross-boundary coupling, dependency-direction leaks, and design debt, generating a structured report of prioritized, actionable fixes.

What severity levels are used for reporting architectural boundary violations?▼

Architectural boundary violations are reported using P0 through P3 severity levels, categorizing issues by criticality to help teams systematically resolve cross-layer coupling and production risks with targeted remediation guidance.