debugging▌

This starts both backend (Streamlit/Python) and frontend (Vite/React) with hot-reload. The app URL is printed on startup (default http://localhost:3001; 3000 is reserved for manual make frontend-dev; it may use 3002+ if other debug sessions are running). Avoid pinning VITE_PORT unless you have a specific hard requirement (last resort).

If "Index is stale" → run npx gitnexus analyze in terminal.

Systematic bug isolation and root cause analysis through hypothesis-driven debugging methodology. \n \n Applies five-step workflow: reproduce, isolate, hypothesize and test, fix, and prevent through regression tests \n Includes language-specific debugger guidance (Python pdb, Node.js Inspector, Go delve) and advanced strategies like git bisect for regression hunting \n Enforces strict constraints: reproduce first, test one hypothesis at a time, document findings, and remove debug code before com

Guides systematic root-cause debugging for tests, builds, and unexpected errors.

Tests in real browsers using Chrome DevTools MCP for debugging and inspecting web applications.

Structured debugging methodology that mandates root cause investigation before attempting any fixes. \n \n Four-phase process: root cause investigation, pattern analysis, hypothesis testing, and implementation with mandatory test cases \n Requires completing Phase 1 (evidence gathering, error analysis, data flow tracing) before proposing any fixes; blocks symptom-based patching \n Includes diagnostic instrumentation guidance for multi-component systems and backward call-stack tracing techniques

Capture a full DevTools-protocol trace of any browser automation for debugging and analysis.

A collection of systematic debugging methodologies that ensure thorough investigation before attempting fixes.

Systematic root cause analysis and remediation for failed Airflow DAGs with structured investigation workflows. \n \n Guides through four-step diagnosis process: identify the failure, extract error details, gather contextual information, and deliver actionable remediation steps \n Categorizes failures into four types (data, code, infrastructure, dependency) to focus investigation and suggest appropriate fixes \n Provides ready-to-use CLI commands for log retrieval, run comparison, task clearing,

Debugging tools for Turso database using bytecode comparison, logging, and deterministic simulation. \n \n Bytecode comparison workflow identifies whether behavior differences stem from code generation bugs or VM/storage layer issues by comparing SQLite and Turso EXPLAIN output \n Logging via RUST_LOG environment variable captures detailed traces from turso_core and simulator components during test runs \n ThreadSanitizer stress tests detect threading issues across configurable thread counts and