Skip to content

Unofficial community registry. Not affiliated with, endorsed by, or sponsored by xAI.

中文

Routines

Draft a changelog from merged work

changelog-draft

Draft a user-facing changelog from the merged titles you exported. Do not publish and do not touch the repository.

for Grok Bot · unofficial, not affiliated with xAI

CNPS0.1.02026-11-18New

Paste this into Grok Bot and say: create this routine.

Create this routine: Draft a changelog from merged work

Trigger: When you put merged titles in changes/merged.md and ask for a changelog draft. Do not push.

What to do:
1. Reads titles from changes/merged.md.
2. Merges duplicates into sentences a user can read.
3. Keeps a title it does not understand and marks it for a person to rewrite.

How:
1. Export this week's merged titles into changes/merged.md. This version does not connect to a code host.
2. The routine keeps an internal ticket id in parentheses rather than pretending it is user language.
3. Write outputs/changelog.md.
4. You publish. The routine does not push or tag.

Rules you can keep:
Read each title in changes/merged.md.
Group into fixed, added, and other. If the group is unclear, use other and keep the original title.
Do not invent a feature that is not in a title.
If an internal word will not make sense to a user, keep the original and mark "needs a person to rewrite".
Write outputs/changelog.md.
Do not push code, do not create a version tag, do not close tickets.

Do not:
- Do not hand over a title that contains a customer name or a secret.
- Do not push to a repository, and do not publish.
- Do not treat the draft as a released changelog.

Paste this into Grok Bot and say: create this routine.

What it does

  • Reads titles from changes/merged.md.
  • Merges duplicates into sentences a user can read.
  • Keeps a title it does not understand and marks it for a person to rewrite.

Who it is for

People writing release notes who already have a list of merged titles.

How to put it in Grok Bot

  1. Export this week's merged titles into changes/merged.md. This version does not connect to a code host.
  2. The routine keeps an internal ticket id in parentheses rather than pretending it is user language.
  3. Write outputs/changelog.md.
  4. You publish. The routine does not push or tag.

Example

Routine snippet

Read each title in changes/merged.md.
Group into fixed, added, and other. If the group is unclear, use other and keep the original title.
Do not invent a feature that is not in a title.
If an internal word will not make sense to a user, keep the original and mark "needs a person to rewrite".
Write outputs/changelog.md.
Do not push code, do not create a version tag, do not close tickets.

Connectors it needs

No connector.

Safety and permissions

  • Do not hand over a title that contains a customer name or a secret.
  • Do not push to a repository, and do not publish.
  • Do not treat the draft as a released changelog.

Risk: Medium

Questions

Why not read Git directly?

This version has no code-host connector. An export lets you remove titles that should not be in the notes.

The titles are in English and the notes should be in Chinese.

Set the output language on the first line. Do not mix the two unless you asked for both.