my blog https://overreacted.io

maybe better commit messsages

Changed files
+7 -1
+7 -1
CLAUDE.md
··· 58 58 - `app/[slug]/mdx.js` - Custom remark plugin for executable code blocks 59 59 - `next.config.js` - Static export configuration 60 60 - `public/[slug]/index.md` - Post content files with frontmatter 61 - - `public/[slug]/components.js` - Optional post-specific React components 61 + - `public/[slug]/components.js` - Optional post-specific React components 62 + 63 + ## Commit Messages 64 + 65 + Write commit messages and PR descriptions as a humble but experienced engineer would. Keep it casual, avoid listicles, briefly describe what we're doing and highlight non-obvious implementation choices but don't overthink it. 66 + 67 + Don't embarrass me with robot speak, marketing buzzwords, or vague fluff. You're not writing a fucking pamphlet. Just leave a meaningful trace so someone can understand the choices later. Assume the reader is able to follow the code perfectly fine.