code-review(23)
- / Date/ Name
- My Auto-Merge Shipped Unfixed Code Because 'Threads Resolved' Won a Race Against 'Fix Committed'
- AI code needs a receipt
- My agent claimed a test suite that did not exist
- The merge gate was built to avoid loops, not to define done
- An AI reviewer's silence is not a yes
- Outdated means the lines moved, not that you fixed it
- The comment count was lying to me
- Green CI is a grammar check, not a fact check
- The admin override is a different trust context
- The pipeline is the review
- Put the dumb checks in the blocking path
- My merge gate counted comments instead of asking GitHub
- Silence is not approval
- A comment count is not a merge verdict
- Green CI is necessary, not sufficient
- 'Threads resolved' is not 'the fix is in the code'
- Make your AI reviewer argue with itself
- CODY has to prove itself wrong first
- My passing tests encoded the fail-open bug as correct behavior
- Agentic engineering, part 2: adversarial code review that loops until clean
- Agentic engineering, part 3: tracing every code path before it becomes a bug
- I built a bug-hunting loop that doesn't quit: the BugBot methodology
- Why the same code looks different from every angle: BugBot lessons learned