validate-sibling-dependency

Validate module dependencies against ADR-020 Sibling Dependency Law.

Updated Nov 24, 2025
One-click install
npx skills add https://github.com/carlo-spada/xentri --skill validate-sibling-dependency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-sibling-dependency
Source: https://github.com/carlo-spada/xentri/tree/main/.claude/skills/validate-sibling-dependency
Command: npx skills add https://github.com/carlo-spada/xentri --skill validate-sibling-dependency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In complex, modular projects, unchecked dependencies can lead to a tangled, unmaintainable architecture, slowing down development and increasing bugs. This skill enforces strict dependency rules, ensuring a clean, scalable system and reducing future refactoring efforts.

Core Features & Use Cases

  • Automated Dependency Validation: Checks module dependencies against the Sibling Dependency Law (ADR-020), preventing architectural drift.
  • Architectural Guidance: Provides a clear decision tree and resolution options for dependency violations, guiding you to compliant solutions.
  • Prevents "Dependency Spaghetti": Ensures entities only depend on siblings or inherit access from common ancestors, maintaining a clear, hierarchical structure.
  • Use Case: When you propose a new module or interface, Claude will automatically validate its dependencies against the project's architectural rules. It will flag any violations before they become problems and suggest how to fix them, saving you from costly architectural mistakes and ensuring project stability.

Quick Start

"Review the proposed dependencies for the new 'UserAuth' module and ensure they comply with ADR-020."

Frequently Asked Questions about validate-sibling-dependency

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

FAQPage Schema
How do I validate module dependencies in a monorepo to prevent architectural violations?

Module dependency validation enforces the Sibling Dependency Law (ADR-020), ensuring entities depend only on siblings or inherit access through common ancestors. This prevents tangled architectures and maintains a clean, hierarchical structure across your codebase.

What is the Sibling Dependency Law and why does it matter for code architecture?

The Sibling Dependency Law restricts modules to depend on siblings and limits requires_interfaces to sibling-only access. It enforces single-parent inheritance, reducing dependency chaos and ensuring architectural integrity as your project scales.

How do I check if a new module's dependencies comply with ADR-020?

Use the automated validation script to review proposed module dependencies against ADR-020 rules. It flags violations, reports them as redesign-required, and provides a decision tree with resolution options to guide compliant architecture.

Can I use dependency validation across both docs/strategy and docs/platform modules?

Yes, the Sibling Dependency Law validation applies across your entire monorepo, including docs/strategy and docs/platform. It assesses ADR-020 conformance consistently and reports cross-module relationship violations.

What happens when my module dependencies violate the Sibling Dependency Law?

Violations are flagged as redesign-required with a clear decision tree showing how to restructure dependencies. Common solutions include accessing dependencies through inherited common ancestors or refactoring modules to true sibling relationships.