e2e-wiring-review

Audit user-facing flows from input to output across apps, APIs, and databases with cited evidence.

157|12|Updated Feb 2, 2026

Search Tags:#audit #runtime #traceability #wiring #code-path #e2e-wiring

Ready to run

npx skills add https://github.com/dcosson/h2 --skill e2e-wiring-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: e2e-wiring-review
Source: https://github.com/dcosson/h2/tree/main/internal/config/templates/styles/opinionated/skills/e2e-wiring-review
Command: npx skills add https://github.com/dcosson/h2 --skill e2e-wiring-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end wiring audits identify gaps where user-facing flows stop short of their intended outcomes, ensuring every entry point and cross-service interaction is verifiably wired and observable.

Core Features & Use Cases

End-to-end path enumeration across web apps, APIs, CLIs, databases, and mobile apps.
Evidence-backed tracing with code citations (file:line) to validate wiring and identify dead paths.
Phase-driven verification including runtime checks, persistence, configuration, and test coverage.
Use Case: Audit a checkout flow to confirm the order is created, stored, and reported to analytics with no dead ends.

Quick Start

Run the auditor against your component to begin tracing every user-facing entry point end-to-end.

Frequently Asked Questions about e2e-wiring-review

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

FAQPage Schema

How do I trace end-to-end wiring across web apps, APIs, and databases to find dead paths?▼

End-to-end wiring audits trace user-facing flows from entry points through controllers, services, and data stores to detect dead paths. This approach uses evidence-backed code citations to verify coverage across web apps, APIs, CLIs, and databases.

What is phase-driven verification for auditing software code paths?▼

Phase-driven verification is an auditing method that checks runtime states, persistence, configuration usage, and test coverage in distinct phases. It confirms every cross-service interaction is verifiably wired and observable using citations to code paths.

How do I verify that a user-facing flow like a checkout process is fully wired to the database?▼

To verify a checkout flow is fully wired to the database, audit the end-to-end path to confirm the order is created, stored, and reported. The audit traces each interaction from user entry through services to validate persistence with no dead ends.

Does end-to-end wiring tracing work for mobile and desktop applications?▼

Yes, end-to-end wiring tracing applies to mobile and desktop applications, as well as web apps, APIs, CLIs, and databases. It enumerates paths across these platforms to confirm every entry point is verifiably wired from input to output.

Why does my application have dead paths in cross-service interactions?▼

Dead paths in cross-service interactions occur when user-facing flows stop short of their intended outcomes. An end-to-end wiring audit identifies these gaps by tracing each interaction from user entry through controllers and data stores with code citations.

What is the best way to audit runtime states and configuration usage in software systems?▼

The best way to audit runtime states and configuration usage is through phase-driven end-to-end wiring verification. This method requires evidence-backed claims with citations to code paths, tests, and runtime states to confirm wiring and configuration usage.