skills.rest
robotijn
robotijnCOMMUNITY
Explore all skills by this author →
GitHub

architecture-checker

Detect circular dependencies, layer breaches, and forbidden imports across codebases.

3|2|Updated Jan 23, 2026
Search Tags:#code quality#dependency analysis#module boundaries#architecture validation#circular dependency detection#layer enforcement#tech debt prevention
One-click install
npx skills add https://github.com/robotijn/ctoc --skill architecture-checker
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-checker
Source: https://github.com/robotijn/ctoc/tree/main/skills/quality/architecture-checker
Command: npx skills add https://github.com/robotijn/ctoc --skill architecture-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Software projects accumulate hidden structural tech debt when architectural rules (dependency directions, module boundaries, layer separation) are violated, leading to brittle codebases that are hard to maintain, test, and scale as the team and product grow.

Core Features & Use Cases

  • Multi-pattern enforcement: Supports layered, hexagonal, clean, modular monolith, and vertical slice architectural patterns, with configurable dependency direction rules stored in a project-level architecture rules file.
  • Comprehensive violation detection: Identifies circular dependencies, leaky abstractions, god modules, forbidden imports, cross-module internal access, SQL schema boundary violations, and high blast radius changes.
  • Use Case: For a team building a modular monolith SaaS, this skill catches when a billing module accidentally imports code from an iam module's internal directory, or when domain logic imports a database driver, preventing structural rot before it reaches production.

Quick Start

Use the architecture-checker skill to scan your codebase for dependency direction violations and circular imports after making structural changes to your project.

Frequently Asked Questions about architecture-checker

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

FAQPage Schema
How do I detect circular dependencies and module boundary violations in my codebase?▼

Architecture validation identifies circular dependencies, layer breaches, and forbidden imports by scanning your codebase against configurable dependency direction rules. It prevents structural tech debt by catching violations like cross-module internal access before they reach production.

What is the best way to enforce layer separation in a modular monolith?▼

The best way to enforce layer separation in a modular monolith is applying a configurable architecture rules file that defines strict dependency directions. This validates your specific architectural pattern to ensure domain logic never imports infrastructure code directly.

Does architecture validation work with hexagonal architecture and clean architecture patterns?▼

Yes, architecture validation works with hexagonal and clean architecture patterns. It supports multi-pattern enforcement for layered, hexagonal, clean, modular monolith, and vertical slice patterns across 7 supported programming languages and SQL schema boundaries.

How do I prevent leaky abstractions and god modules from accumulating during development?▼

Prevent leaky abstractions and god modules by running automated structural checks during stage transition quality gates. This identifies high blast radius changes and architectural violations early, blocking phase advancement until the structural issues are resolved.

Can I check SQL schema boundaries and dependency directions across multiple programming languages?▼

Yes, you can check SQL schema boundaries alongside dependency directions across 7 supported programming languages. The validation process enforces project-specific rules to prevent cross-module internal access and structural violations regardless of the language used.

What happens when structural tech debt and layer breaches are found during a phase transition?▼

When layer breaches are found during a phase transition, the validation emits critical findings that block phase advancement. This strict warnings-are-bugs policy ensures all circular dependencies and forbidden imports must be resolved before proceeding.

Related Skills

Explore More Software Engineering Skills→
hproofhproof

full-scan

Automates macro-level codebase scanning to map modules and generate a project structure document.

Community
Intermediate
baphledbaphled
1

fix-architecture

Diagnose and fix software architecture violations with guided, test-backed refactoring.

Community
Intermediate
robotijnrobotijn
3

quality-gate

Coordinate quality checks across tiered gates in CI/CD pipelines.

Community
Advanced
keremtoker468-dotcomkeremtoker468-dotcom

semgrep-rule-creator

Create Semgrep rules using a test-first methodology with AST analysis and taint mode.

Community
Advanced