Architecture Drift Detector FAQs

Question 1

What documents does the skill use to verify decisions?

Accepted Answer

The skill scans for accepted Architecture Decision Records (ADRs) located in the docs/decisions/ directory and extracts constraints to compare against the source code.

Question 2

How does arch-drift determine module restrictions?

Accepted Answer

It utilizes a hierarchical rule set where 'app' can depend on 'lib' and 'core', 'lib' can only depend on 'core', and 'core' cannot have internal dependencies. Exceptions can be manually declared in the project's CLAUDE.md file.

Question 3

What is the difference between an Error and a Warning in the report?

Accepted Answer

An Error is a clear violation of core dependency direction (e.g., core importing from app), while a Warning indicates a probable violation or an undeclared lib-to-lib dependency.

Question 4

Can I use this skill in my CI/CD pipeline?

Accepted Answer

Yes, by using the --strict flag, the skill will return a non-zero exit code if any error-level violations are found, allowing you to fail builds that drift from the architecture.

Question 5

Does it support cross-library dependencies?

Accepted Answer

By default, lib-to-lib dependencies are flagged as warnings unless they are explicitly declared in the ## Dependencies section of your module's CLAUDE.md file.

Architecture Drift Detector

주요 기능

사용 사례

Architecture Drift Detector

주요 기능

사용 사례