BotShelf Vampire BOTSHELF VAMPIRE Register

GROK BOT TOOLS · ROUTINE BRIEF

Weekly release notes from merged changes

Drafts weekly release notes from changes merged since the previous completed review and returns them in chat. Stops before publishing, tagging, creating a release or changing the repository.

No sign-upRoutine briefGrok BotReleasesUntested

Where it goes

Send it as a message to the Bot that should own the job. On a phone: the Bot's profile, Routines, Add routine. A new routine waits for its next scheduled time, so read When to run and press Test once before you rely on it.

First three moves

  1. Fill the weekly schedule and connected repository, then send the text to the Bot that should own the draft.
  2. Read "When to run" and use Edit if the weekday, time or time zone is wrong.
  3. Use Test once on a repository you can inspect. It does real work; compare draft references and interval boundaries with merge records, and check that no tag or release was created.

Where it stops

Blanks to fill

BlankWhat goes there
[DAY]Weekday for preparing the draft.
[TIME]Local time for the weekly draft.
[TIMEZONE]Time zone for the weekly schedule, written out.
[REPO]Connected repository whose merged changes should be read.

Replace every bracket. Leave none behind.

The text

Download text.md Fork it Results & questions

Set up a routine to draft weekly release notes from merged changes, using these unofficial instructions.

Owner: you (this Bot).
When: every [DAY] at [TIME], time zone [TIMEZONE].
Input: changes merged in [REPO] since the previous completed coverage recorded in this chat, through this scheduled run. On the first run, cover the preceding seven days and state the boundaries.
Work: read merge records and relevant diffs. Group changes by user impact, combine related work and account for reversions. Give every note its merge identifier and revision. Flag compatibility questions separately. Exclude unmerged work. Do not invent version numbers, release dates or deployment status; a merged change may not be live.
Result: a release notes draft in this chat, with interval, change groups, references, questions and coverage status.

Approval boundary:
- Keep the draft here. Do not publish, edit files, create tags or releases, merge, push or deploy.
- Stop before sending messages, purchasing, paying, deleting or changing production.

If the source is missing or stale:
- Report unreadable history, changed revisions or a missing previous coverage record. Do not silently replace an unknown interval with seven days.
- If the readable interval has no merges, say so with its boundaries.

If partly complete, report covered and unread changes here with reasons; retain the previous completed boundary. Do not retry independently.

Running twice must be safe: retain the same interval, reuse notes by repository and merge identifier, and add no duplicate draft for completed coverage.

After setup, tell me exactly what "When to run" shows, including weekday, time and time zone.

License: MIT. Free, no sign-up. Use is at your own risk. BSV does not run it or set it up for you.

What it adds to the official page

The official page describes scheduled preparation and safe repeat runs. This request adds a merge-based reporting interval, source references for each note and preservation of the last completed boundary after partial coverage.

Sources

The product facts in this text come from these official pages, read on 2026-11-18. Products change: when a page and this text disagree, the page is right.

All Grok Bot tools Download all (ZIP) Search the shelf