check-cross-layer

Validate cross-layer data flow, code reuse, and import consistency across architectural layers.

92|8|Updated May 15, 2026
One-click install
npx skills add https://github.com/LonelyHerbivore/Trellis-Herbivore --skill check-cross-layer-lonelyherbivore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-cross-layer
Source: https://github.com/LonelyHerbivore/Trellis-Herbivore/tree/main/packages/cli/src/templates/codex/skills/check-cross-layer
Command: npx skills add https://github.com/LonelyHerbivore/Trellis-Herbivore --skill check-cross-layer-lonelyherbivore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents post-implementation defects caused by incomplete updates across multiple architectural layers, such as broken data flow, inconsistent types/schemas, wrong dependency paths, or duplicated constants.

Core Features & Use Cases

  • Cross-Layer Data Flow Verification: Validates end-to-end read/write flow across layers (DB → Service → API → UI) and checks error propagation and loading/pending handling when changes span 3+ layers.
  • Code Reuse & Duplication Detection: Ensures constants/config values and similar code patterns are reused or extracted correctly after hardcoded-value changes or batch edits.
  • Import/Dependency and Same-Layer Consistency Checks: Confirms new files use correct import paths, avoids circular dependencies, and keeps formatting/display logic consistent within the same domain concept.

Quick Start

Run the cross-layer check after you complete an implementation that touches shared constants/configs or modifies files across three or more layers, then report which dimensions are triggered and what issues you find with concrete fix suggestions.

Frequently Asked Questions about check-cross-layer

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

FAQPage Schema
How do I verify cross-layer data flow after modifying shared constants in my codebase?

Verify cross-layer data flow by validating end-to-end read/write paths across DB, Service, API, and UI layers, while checking that type/schema and error propagation remain consistent across all affected usage sites.

When do I need to check architecture consistency for multi-layer code changes?

Check architecture consistency when changes span 3 or more architectural layers, involve batch file modifications, or create new utility functions, ensuring all affected usage sites and dependency paths are updated.

How do I detect code duplication and inconsistent import paths after batch file modifications?

Detect code duplication by ensuring hardcoded constants and config values are extracted correctly, and verify import paths to confirm new files avoid circular dependencies and maintain correct dependency routing.

Does cross-layer validation work for checking error propagation and loading states across architectural layers?

Cross-layer validation works for checking error propagation and loading or pending handling across architectural layers, identifying missed updates or mismatches and providing actionable fix suggestions.

What is the best way to catch cross-layer misses before shipping post-implementation changes?

The best way to catch cross-layer misses is running a consistency check after implementation to validate data flow, code reuse, and import paths, reporting triggered dimensions and concrete fix suggestions.

Why does same-layer consistency break when updating display logic within a single domain concept?

Same-layer consistency breaks when formatting and display logic within a domain concept are not kept aligned during updates, requiring consistency checks to identify mismatches and suggest actionable fixes.