Archive
Every issue, newest first. The headline leads each row because that is what distinguishes one day from another — a grid of dated cards would tell you less in six times the space. 13 of 59 issues so far were quiet days, and said so.
Write an AGENTS.md that earns its place in the context
What leaves your repository when you use an AI coding assistant?
Before an AI refactor, record what the old code actually does
Claude Code vs Codex vs Cursor: choose the workflow you can finish
Give a coding agent credentials without handing over production
A coding-agent handoff should survive a fresh session
Give a coding agent a monorepo task without loading the whole monorepo
Write a coding-agent task brief that can be checked
Run coding agents in GitHub Actions without trusting every issue
Diagnose flaky tests before a coding agent “fixes” CI
Evaluate coding agents on your repository with a reusable task card
Verify AI-generated frontend changes with Playwright visual checks
Build a reproducible development environment for your coding agent
Review an AI-generated database migration before it touches real data
Review an MCP server before connecting your coding assistant
Skills, MCP or repository instructions? Start with the missing piece
How to test AI-written code without copying its assumptions
Verify AI-suggested packages before installing them
When a local coding model makes sense
Your agent finished. Can you explain the change?
Signal history — 30 issues
height = how much actually happened · click a column to open that issue2026-09-14today
quiet day — we say so and keep it short something breaking landed