How a Team's AI Coding Flow Should Be Wired
A change lands in review with everything green. The rules pass, the types check, the tests are close to the ones I'd have asked for.
Tagged team-workflow
-
-
The Other Intent
The business intent, what we're accomplishing, goes in the PR description. Solved problem; we've had a text box for it since forever.
-
The Nit Was Never Optional
Read that definition again. It's one of the most widely-cited code-review standards telling reviewers how to flag a small issue: say the author should fix it…
-
Your Skills Are a Codebase, Not a Junk Drawer
I asked the agent to review a diff. Two skills woke up and started fighting over whose job it was.
-
Skills are one-offs. If you want an ecosystem, you need plugins.
You wrote a skill. It's good. Now you want it to lean on another skill — call it, require it, ship the two together so installing yours pulls in the one it…
-
Teaching the Reviewer
I was building a code-review tool. Nothing fancy — read the diff, flag what's wrong, the job I do by hand a dozen times a week.
-
A Description Can't Replace the Code
A description is a compression, and it drops the omissions it doesn't know it made — the case not handled, the check not added.
