write for /read
Show us how you actually work.
/read publishes developers writing about using AI to ship real work. Same rule as the channel: no hype, just what works.
What we're looking for
- A setup you use every day: skills, agents, MCP servers, prompts, hooks, workflows.
- Something that broke, why, and what fixed it.
- Before-and-after: the same task done by hand and with AI, with the real numbers.
- Teaching a junior dev (or yourself) a new way of working.
What we pass on
- Hype, predictions, and "10 prompts that will change your life."
- Rewritten docs or press releases.
- Posts that are mostly a pitch for your product. Mentioning what you built is fine.
- Unedited AI output. Use AI to help, but the experience and the voice have to be yours.
How it works
- Sign in with GitHub and start a draft. Drafts are private.
- Write in Markdown. Code blocks get syntax highlighting; paste images straight in.
- Hit Submit for review. The editor reads every story.
- It gets published, or comes back with notes. Edits to a live story go through the same review, and the live version stays up meanwhile.
What you get
Your story goes out under your name, with your profile linking to your own site and GitHub, so it works as a portfolio piece and a backlink. The best story each week gets featured in the Prompt & Commit email, and the standouts get a mention on the channel.
The first 20 writers I publish become founding writers. That means a founding writer badge on your profile and your stories for good, plus a sticker pack in the mail.
Your work stays yours
You keep the rights to what you write. By publishing here you give Prompt & Commit permission to show it on /read, in the newsletter, and in promotion of the story with credit to you. You can take a story down any time.