review-architecture

Review monorepo layouts, workspace dependencies, and Turborepo task graphs.

18|4|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/louisbrulenaudet/monorepo-template --skill review-architecture-louisbrulenaudet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-architecture
Source: https://github.com/louisbrulenaudet/monorepo-template/tree/main/.agents/skills/review-architecture
Command: npx skills add https://github.com/louisbrulenaudet/monorepo-template --skill review-architecture-louisbrulenaudet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the complexity of maintaining a clean monorepo by identifying architectural drift, circular dependencies, and configuration inconsistencies that degrade project scalability.

Core Features & Use Cases

  • Dependency Analysis: Validates workspace dependency direction and detects circular imports between apps and packages.
  • Task Graph Verification: Ensures Turborepo task graphs are acyclic and cache boundaries are correctly defined.
  • Use Case: Use this during a refactoring phase to ensure that new packages adhere to the established monorepo boundaries and that build tasks remain optimized for CI/CD performance.

Quick Start

Invoke the review-architecture skill to perform a full architectural audit of the current monorepo structure.

Frequently Asked Questions about review-architecture

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

FAQPage Schema
How do I detect circular dependencies in a Turborepo monorepo?

Analyzing workspace dependency direction helps detect circular imports between apps and packages in a monorepo. This architectural review validates boundary adherence to prevent coupling and ensure clean dependency graphs across the workspace.

What causes architectural drift in monorepos and how do I check for it?

Architectural drift in monorepos is caused by configuration inconsistencies and boundary violations between apps and packages. An architectural health check identifies this drift by evaluating workspace layouts, Makefile usage, and public API surfaces to maintain project scalability.

How do I validate Turborepo task graphs for CI/CD performance?

Validating Turborepo task graphs for CI/CD requires ensuring the graphs are acyclic and cache boundaries are correctly defined. This optimization prevents redundant build tasks and maintains the integrity of the build system.

Does this architecture review work with TypeScript monorepos using Turborepo?

Yes, this architecture review works with TypeScript monorepos using Turborepo by validating dependency directions and task graph integrity. It ensures consistent configurations across applications and shared packages to prevent circular dependencies.

When should I run an architectural audit of my monorepo layout?

You should run an architectural audit of your monorepo layout during refactoring phases to ensure new packages adhere to established boundaries. It validates build system integrity and public API surfaces to prevent coupling and circular dependencies.