deep-debug-api

Trace API request flow from React frontend to database to locate data shape divergences.

6|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/anotherben/claude-harness --skill deep-debug-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-debug-api
Source: https://github.com/anotherben/claude-harness/tree/main/skills/b-deep-debug-api
Command: npx skills add https://github.com/anotherben/claude-harness --skill deep-debug-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This diagnostic skill helps engineers identify root causes of API endpoint crashes and frontend rendering issues by tracing the data flow from the React frontend through Express routes to the service layer and database, without modifying any code.

Core Features & Use Cases

  • Trace request flow from frontend to database to locate where data shapes diverge and where nulls appear.
  • Identify common crash patterns caused by missing null guards, json_agg nulls, or schema changes, and guide defensible fixes—without touching production code.
  • Use in scenarios where an endpoint consistently fails for specific records or data shapes, while other records work normally.

Quick Start

Run an investigation by loading a failing request example into the debugger and following the step-by-step trace to isolate the crash.

Frequently Asked Questions about deep-debug-api

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

FAQPage Schema
How do I trace an API crash from the frontend to the database to find the root cause?

Tracing an API crash involves following the request flow from the frontend through Express routes to the database to identify where data shapes diverge. This diagnostic process isolates the exact point of failure without modifying production code.

Why does my Express API endpoint fail for specific records but work for others?

An Express API endpoint may fail for specific records due to missing null guards or json_agg edge cases in the service layer. Tracing the request flow reveals where nulls appear in the data shape and causes the frontend rendering to crash.

How do I debug json_agg null values causing crashes in my API route?

Debugging json_agg null values requires tracing the route flow from the Express service query to the frontend formatting layer. This identifies where nulls are introduced and pinpoints the missing null guards responsible for the crash.

Can I run read-only API diagnostics without modifying my production code?

Read-only API diagnostics can be run safely without modifying production code. The investigation traces the frontend to database request flow to locate data shape divergences and identify common crash patterns like missing null guards.

What is the best way to find where data shape diverges in a full stack request flow?

The best way to find where a data shape diverges is running a full request trace from the frontend formatting to the database service query. This isolates the specific record properties triggering schema changes or json_agg nulls.

How do I identify missing null guards in my API service layer after a schema change?

Identifying missing null guards after a schema change involves tracing the API route flow to see where unexpected nulls appear in error-bound records. The diagnostic trace highlights the exact service query lacking adequate null protection.