nacl-tl-verify-code

Trace end-to-end data flow from database to UI to verify code changes.

23|2|Updated Apr 10, 2026

Search Tags:#frontend #backend #end-to-end #verify #code-analysis #data-flow

Ready to run

npx skills add https://github.com/ITSalt/NaCl --skill nacl-tl-verify-code

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: nacl-tl-verify-code
Source: https://github.com/ITSalt/NaCl/tree/main/nacl-tl-verify-code
Command: npx skills add https://github.com/ITSalt/NaCl --skill nacl-tl-verify-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Traces the full data flow from database to user interface to ensure changes implement the intended behavior and do not introduce regressions.

Core Features & Use Cases

End-to-end data-flow tracing across backend (DB → service → route → hook → component) and frontend (API client → hook/store → component → UI).
Distinguishes between correctness verification and quality review, and provides PASS / PASS_NEEDS_E2E / FAIL outcomes.
Use Case: verify a UC implementation update to ensure new fields or flows reach the UI correctly.

Quick Start

Run /nacl-tl-verify-code UC028 to verify a UC task and inspect the full data-flow trace.

Frequently Asked Questions about nacl-tl-verify-code

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

FAQPage Schema

How do I verify end-to-end data flow correctness from database to UI?▼

End-to-end data flow verification traces changes from DB through backend services and routes to frontend UI components, confirming type alignment, null handling, and error propagation to ensure correctness and prevent regressions.

What is the difference between code correctness verification and code quality review?▼

Code correctness verification confirms that data flows reach the UI as intended and match API contracts, whereas quality review evaluates broader code structure and standards.

How do I check if a new backend field correctly propagates to the frontend component?▼

To check field propagation, trace the data flow from the database through the API client and hook or store to the UI component, validating type alignment and null handling at each layer.

What do I need to perform end-to-end task-based code verification?▼

You need task descriptions, access to the relevant code paths, and consistent API contracts to perform end-to-end task-based code verification across the backend and frontend stack.

How do PASS_NEEDS_E2E and FAIL outcomes differ during data flow tracing?▼

A PASS_NEEDS_E2E outcome indicates data flow logic is correct but requires runtime confirmation, while a FAIL outcome identifies breaks in type alignment, null handling, or error propagation.