debug

To debug issues without editing files, trigger a structured investigation session that collects context from minikube pod logs, PostgreSQL nonprod state, and recent git history. It surfaces actionable findings to triage unexpected behavior during manual testing.

Correlating git history with database state involves reviewing recent code updates alongside PostgreSQL nonprod data integrity checks. This coordinated diagnostic approach helps trace root causes by matching anomalies in database state with specific version control changes.

Yes, you can inspect PostgreSQL nonprod state to verify data integrity and migrations. The diagnostic session retrieves database state without modifying files, allowing you to check for data anomalies while testing your implementation.

Start a debugging session by triggering the debug command to bootstrap a focused investigation. It automatically coordinates the collection of minikube pod logs, database state, and git history to report failures and anomalies for triage.

Yes, this troubleshooting approach works for local clusters by investigating minikube pod logs to identify failures. It traces root causes by coordinating container state diagnostics with version history and database checks without editing files.

The limitation of a non-editing debugging bootstrap is that it strictly collects and reports diagnostic context without modifying source files. It surfaces findings for triage but does not apply fixes to logs, PostgreSQL state, or git history.