check-cross-layer

Run git status and git diff --name-only to identify changed files, then use grep to search for the modified values or patterns across the source tree. This reveals all usage sites that may need matching updates.

Trace the read flow from database through service and API to UI, and the write flow in reverse. Confirm types and schemas pass correctly between layers, errors propagate to callers, and loading states are handled at each layer.

Run it after finishing implementation but before committing, especially when changes touch three or more layers, modify shared constants, create new utility functions, or apply batch edits across multiple files.

Search the source directory with grep for the exact value you plan to change. If two or more locations define the same value, extract it into a shared constant and update every usage site.

A checklist only catches issues in the dimensions you select and depends on thorough grep searches. It does not execute tests or detect runtime behavior, so it should complement automated testing rather than replace it.