• QUIET ENGINESstash
Browse
  • lLibrary Home
Library
  • pPrompts
    • sStack
    AboutPrivacyReport
    QE-0047-A·————-——-——T——:——:——
    Owner
    • QUIET ENGINESstash
    Browse
    • lLibrary Home
    Library
    • pPrompts
      • 1Counsel
      • 2Design
      • 3Dev
      • 4DJ
      • 5Image
      • 6Paper
      • 7PStack
      • 8suffixes
      • 9Worlds
      • Writing
    • sStack
    AboutPrivacyReport
    1. Library
    Authenticate. Currently visitorVisitorAuthenticate
    • QUIET ENGINESstash
    Browse
    • lLibrary Home
    Library
    • pPrompts
    AboutPrivacyReport
    1
    Counsel
  • 2Design
  • 3Dev
  • 4DJ
  • 5Image
  • 6Paper
  • 7PStack
  • 8suffixes
  • 9Worlds
  • Writing
  • sStack
  • Prompts

    Release Writing

    Updated Sep 18, 2026

    From the git log / diff I paste (or from git log / git diff on this repo), write the human-facing release note.

    Audience: {Owner | Visitor | Agent}. One audience only. Lead with what changed for them. Then what to do. Then what broke. No "we're excited". No "various improvements". No feature list that restates commit subjects.

    If a change is internal-only, omit it or put it in a trailing Internals line, not the lead.

    Also write: one-line commit subject, and the changelog bullet (sentence case, period at the end, names the user-visible change).

    Do not invent features that are not in the diff.

    Release note, commit subject, and changelog bullet from the actual diff.