observe-before-editing

Debug code errors by manually running commands to verify actual system behavior and checking log files. This approach prevents incorrect code modifications by ensuring your actions are based on empirical evidence rather than assumptions.

Verifying system outputs prevents wasted effort by ensuring code modifications are based on actual observed states. Confirming the existence and content of generated directories and files validates true behavior before you make changes.

The best way to triage errors is to check cache directories and log files to pinpoint the exact cause of failure. Manually running the failing command confirms actual output and isolates the issue before you edit code.

You need to check logs and cache directories when a process fails and you suspect incorrect code modifications. Manually verifying these system states helps diagnose the exact cause of the failure before you attempt a fix.

Yes, output verification works for diagnosing process failures without dependencies by directly checking generated directories, files, and logs. It guides you to manually run commands to confirm system behavior empirically.