check-cross-layer

To verify cross-layer code consistency, you need to validate data flow paths, import statements, and shared constants across API, service, and UI layers. This check detects missed updates and inconsistencies after modifying shared configurations or batch files.

Preventing circular dependencies requires import path validation across your architectural layers. This process ensures correct import statements and verifies that new files do not create conflicting data flow paths or duplicated constants within the codebase.

Checking for duplicated constants involves running a code reuse analysis across your architectural layers. This detects repeated utilities or shared configurations and suggests centralizing them to maintain cross-layer consistency and prevent divergent behavior.

You need cross-layer validation after modifying shared constants, configs, batch files, or creating new utilities that affect three or more architectural layers. It confirms that all related data flows, imports, and same-layer behaviors remain aligned.

Yes, the cross-layer validation process runs without requiring any external dependencies or components. It directly analyzes your repository's code changes, import paths, and data flow to identify inconsistencies across architectural layers.

Updating shared configurations causes bugs when cross-layer data flow paths are not fully verified. Same-layer consistency checks and import validation are needed to ensure all related files across API, service, database, and UI layers are updated correctly.