vc-debug

Follow the four-phase framework: investigate the root cause by reading errors and reproducing consistently, analyze patterns against working code, test one hypothesis with a minimal change, then implement a single fix with a failing test case. Never apply fixes before completing root-cause investigation.

Use the included find-polluter.sh bisection script with the polluted path and a test file pattern. It runs each test individually and stops at the first one that creates the unwanted file or directory, identifying the exact polluter.

Use the gh CLI to list recent runs, view failed job logs with gh run view --log-failed, and match errors against common patterns like environment differences, flaky tests, timeouts, or secret misconfiguration. Correlate failures with recent commits and config changes.

Yes, it includes a performance diagnostics reference covering bottleneck identification across network, application, database, and filesystem layers. It provides PostgreSQL queries for pg_stat_statements, EXPLAIN ANALYZE usage, and a prioritized optimization strategy.

Never claim completion without fresh verification evidence. The verification protocol requires running the actual test or build command, reading the full output and exit code, and only then stating the result with that evidence attached.