{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifuuwdji55a77ecdsvjppxopbwx5qxaplpc7qq6c6c74ndo7yycci",
    "uri": "at://did:plc:3hmagzdut76xycuvulaezm3j/app.bsky.feed.post/3mlvujqmt7js2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreigw3zgtcoposrzq4s5ysjdgsv2tyonizzkpkdfcui3ryynu7iamwe"
    },
    "mimeType": "image/png",
    "size": 72983
  },
  "path": "/2026/05/15/aiassisted-release-notes.html",
  "publishedAt": "2026-05-15T15:07:06.000Z",
  "site": "https://www.manton.org",
  "tags": [
    "lots of native apps",
    "help.micro.blog/t/micro-b…"
  ],
  "textContent": "We have lots of native apps, but I will never use that as an excuse to write generic “bug fixes” release notes. I like including good release notes both for our users and for myself later, as I look back on what we’ve shipped.\n\nStill, it is a lot to keep up with. Lately I’ve been turning to Codex to get me started with a release notes draft. I use a prompt like this:\n\n> Please review all the git commits since the tag “release/3.8.4” and write some release notes for the major changes. Read the release notes from the web page here help.micro.blog/t/micro-b… and follow that style of what is important and how to phrase the changes.\n\nIt’s usually not quite right, a little too verbose, so I can then edit it to fit what I would’ve written by hand anyway. Saves a lot of time.",
  "title": "AI-assisted release notes"
}