check-cross-layer

Verify cross-layer changes for missed update sites and type mismatches.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/SDDKKK/Trellis_Hiskens_backup_20260413 --skill check-cross-layer-sddkkk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-cross-layer
Source: https://github.com/SDDKKK/Trellis_Hiskens_backup_20260413/tree/main/.agents/skills/check-cross-layer
Command: npx skills add https://github.com/SDDKKK/Trellis_Hiskens_backup_20260413 --skill check-cross-layer-sddkkk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a post-implementation verification checklist to catch overlooked cross-layer bugs such as missed update sites, type/schema mismatches, duplicated constants, incorrect import paths, and inconsistent same-layer behavior that commonly occur when changes span multiple architectural layers.

Core Features & Use Cases

  • Cross-layer data flow checks: Verify read and write flows, error propagation, and loading states across layers to ensure end-to-end consistency.
  • Code reuse and constants validation: Detect duplicated hardcoded values, ensure all usage sites are updated, and recommend extraction to shared constants or utilities.
  • Import and dependency validation: Confirm correct relative/absolute import paths, identify potential circular dependencies, and validate file placement for new modules.
  • Use Case: Run after modifying shared configs, creating new utilities, or batch-editing files that touch API, service, and database layers to find missed change sites and type mismatches.

Quick Start

Run the cross-layer check on your current branch and produce a report listing which dimensions apply, discovered issues, and suggested fixes.

Frequently Asked Questions about check-cross-layer

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

FAQPage Schema
How do I check for cross-layer data flow issues after modifying shared constants?

To check cross-layer data flow after modifying shared constants, run a verification pass to detect duplicated hardcoded values, validate read and write flows, and identify all impacted usage sites for consistent updates.

What is the best way to find missed update sites when edits span multiple architectural layers?

Finding missed update sites across architectural layers requires a post-implementation verification checklist that validates type consistency, confirms correct import paths, and identifies all impacted usage sites to prevent cross-layer bugs.

How do I validate import paths and detect circular dependencies in a large codebase?

Validating import paths and detecting circular dependencies involves confirming correct relative or absolute paths, identifying potential dependency cycles, and validating file placement for newly created modules.

When do I need to run a cross-layer consistency check?

You need a cross-layer consistency check when edits span three or more architectural layers, shared constants or configurations are modified, or after batch file updates and new utility creation to ensure end-to-end data flow correctness.

Does this cross-layer check work for API, service, and database layers?

Yes, the cross-layer check works for API, service, and database layers by validating data flow correctness, type consistency, and error propagation across these layers to ensure end-to-end consistency after batch file updates.

Why does my code break after batch file updates across different layers?

Batch file updates across different layers can break code due to type or schema mismatches, duplicated constants, or incorrect import paths, requiring a cross-layer validation to find missed change sites and fix impacted usage.