Grok BotWorkflowInstruction template

Release Notes Page

Turn a defined range of pull requests or commits into user-facing release notes with traceable evidence, plus a reviewable stable-page update and notification draft.

0 opens · 0 copies

Source credit: stevy_smith

Bot spec
Type
Workflow
Optional tools
GitHub · Stacktree · Slack
Delivery
Copyable instruction template
Updated
Sep 5, 2026

Setup and workflow

Provide version boundaries and deployment evidence. GitHub can be read-only; Stacktree and Slack need write access only for approved publication.

  1. Define the release range and separate undeployed or internal changes.
  2. Review user impact and compatibility notes before approving page updates and notifications.

Input and output example

Illustrative example · not an execution result

Input

Demo: PR 12 fixes CSV export encoding and is deployed; PR 13 adds bulk deletion but is not deployed.

Output

Released fix: CSV exports preserve non-English characters (PR 12). Pending: bulk deletion (PR 13), excluded from released features. The notification includes only the deployed fix.

Limits and failure cases

  • Commit titles alone cannot establish every product behavior.
  • It does not automatically create a weekly job or guarantee a third-party URL forever.

What was verified

Source check · Verified · 2026-09-05
Compared with bots/release-notes-page.md in BotDirectory commit 84dc42af7661. This checks the published entry (prompt or description), not its execution or every original social post.
Prompt rehearsal · Not verified
Editorial review and an illustrative example only; no independent model execution was recorded.
Native Grok execution · Not verified
Native Grok execution, tool permissions and real account operations have not been tested.
Bot link access · Not applicable
This entry is a copyable instruction template, not a verified native Bot installation.

Source and editorial adaptation

Adapted from Release Notes Page in botdirectory.ai (listed contributor: stevy_smith), distributed under MIT. Contributor credit is taken from that repository, not independently authenticated. AI Prompt Card supplies bilingual editing, usage notes and labelled examples. The source link records the upstream version; no endorsement is implied.

Source license and attribution
Bot instructions

Copyable instruction template

Instructions curated or adapted by this site, not a claim to reproduce the native Bot’s internal system prompt. Check setup, tools and limitations before use.

Prepare notes for a specified release. Ask for repository, start/end commits or previous version, actual deployment status, audience, excluded labels and existing changelog URL. Read authorized GitHub data or supplied PR/commit lists; group direct-push commits by change. Describe user-facing benefits or behavior changes and link each item to its PR or commit. Separate features, fixes, breaking changes and internal maintenance. Mark unconfirmed deployments as pending instead of claiming they are live. Show the full notes, a proposed update to the stable page and a Slack notification draft. Write or send only after I approve the exact page, channel and content and the required Stacktree/Slack tools are available. Confirm weekly scheduling separately. Without tools, return Markdown and do not claim a page was updated.

0 opens · 0 copies

Editorial assessment

For teams translating engineering history into public updates. Unlike a commit dump, it separates user-visible changes, internal maintenance and code not yet deployed. Stable URLs depend on the publishing platform, and schedules require setup; a merged PR does not prove users can access the feature.

This directory is an independent, fan-made catalog. It is not affiliated with, endorsed by, or sponsored by xAI or Grok. Grok and related names are trademarks of their respective owners. Live-bot links point to official x.ai pages.

More Grok bots

Related bot prompts

Workflow

New Hire Ramp Plan

Plan first-week introductions, reading and a small verifiable deliverable from role goals and authorized onboarding examples, without automatically scheduling meetings.

0 opens · 0 copies
Research

Competitive Build Researcher

Translate public evidence about named competitors into build trade-offs and an implementation plan, separating observed behavior, technical inference and unvalidated demand.

0 opens · 0 copies