Why /read exists

I started Prompt & Commit to show how I actually use AI on real work. Video is good at showing a terminal. It's bad at the part I care about most, which is everybody else doing this.

Somebody out there already has a better setup than mine. A hook that blocks commits without a ticket number. A skill that writes their release notes. A subagent that does nothing but read logs. On a video, the most room they get is a comment, and comments sink as soon as the next video goes up.

/read is where those go. Developers writing up how they use AI to ship: the skill that finally fired, the agent that deleted the wrong folder, the same task done by hand and with Claude, with the real numbers. Same rule as the channel. No hype, just what works.

I read every story before it goes up. I'm not looking for polish. I'm looking for something only you could write, because you were the one at the keyboard when it happened.

I'll pass on predictions, listicles, rewritten docs, and anything that's mostly a pitch. Mentioning what you built is fine. Unedited AI output isn't. Use it to help you write, but the experience has to be yours.

You sign in with GitHub, write in Markdown, and hit submit. Drafts stay private, and if I send one back, my notes are right there with it. You keep the rights to what you write and can take it down whenever you want. The guidelines have the rest.

The first few stories here are mine, written up from the episodes. I'd rather the next ones weren't.