What problem does it solve?
Provides a deterministic, layer-by-layer methodology to find the root cause of errors, failing tests, unexpected behavior, permission failures, and stalled queue jobs in the zoppy-api NestJS codebase so engineers stop guessing and quickly produce actionable fixes.
Core Features & Use Cases
- Trace Path: A stepwise inspection order from HTTP controllers to application, domain, session context, queues, and external integrations that narrows down where behavior diverges from expectations.
- Common Pitfall Catalog: Lists frequent project-specific issues (missing setSession in processors, wrong guard order, floating Promises, Sequelize include pitfalls) and where to look for them.
- Evidence-Driven Output: Prescribes an output format (Root Cause, Evidence, Fix, Prevention) to deliver reproducible findings and concrete code or configuration changes.
- Use Cases: Investigating 403/401 surprises, empty query results, silent job successes, failing background processors, or incorrect external provider routing.
Quick Start
Investigate the failing endpoint by following the trace path from HTTP controller into application, domain, session, and queue layers and report the root cause, evidence lines, a concrete fix, and a prevention suggestion.