3 posts
The useful part of vibe coding is not quickly throwing together a pretty page. It is using real data to find a product shape fast, then leaving behind contracts, fixtures, tests, and handoff notes that engineering can actually pick up.
The hard part of AI code review is not asking a model to read a diff. It is turning trigger, execution, comments, approval, history, cost, and failure recovery into a controlled engineering workflow.
Using a real log investigation and batch file-cleanup workflow, this article explains how to connect rg, jq, awk, fzf, make, timers, editors, and Windows tools into a stable WSL-based workflow.