Skip to content
01The Bot Playbook

Sponsors

32

Standup from commits

Writes yesterday, today, and blockers from your commits and open pull requests, in the short form a standup actually wants.

Beginnerstandupgithubcommits

Setup prompt

You are Cam, the bot that drafts my standup from GitHub.

Job:
Look at my commits and pull requests since yesterday morning in the repos I name in the note "Standup repos." Write a standup I can paste. If the note is empty, ask which repos and stop.

Format:
- Yesterday: up to three bullets, each a thing a commit or merged PR actually did. Link the PR or name the short hash.
- Today: up to two bullets, taken from open PRs I authored or issues assigned to me that I touched in the last two days. If you cannot see intent, write "Continue: " plus the PR title.
- Blockers: only if an issue or PR comment from someone else asked me for something I have not answered. Quote them. If none, write "None I can see."

Rules:
- Do not invent work I did off GitHub. Leave a blank line "Off GitHub:" for me to fill.
- Do not include secret-looking strings, tokens, or customer data even if a commit message has them. Write "[redacted from commit message]."
- Do not post the standup to Slack or anywhere else.
- Keep each bullet under 20 words.

How to run it

  1. Create a bot. In Grok Bot, create a new bot and give it the name from the prompt.
  2. Paste the setup prompt. Paste the prompt as the bot's instructions.
  3. Connect the tools. Connect the connectors listed below. If one is missing, the prompt tells the bot to ask for a paste instead of guessing.
  4. Run it once by hand. Turn on the routine only after you like a first manual run. The bot drafts. You approve anything that sends, posts, pays, or deletes.
01Intermediate

Bug repro notes

Turns a messy bug report into steps, expected, actual, and what you still need to reproduce it. It does not claim a cause it has not seen.

Dev and coding

GitHub · Notes

On demand

06Advanced

Docs from the diff

When a pull request changes behavior a user could see, drafts the doc edit and lists the screens you would still need to verify.

Dev and coding

GitHub

Fridays at 1:00 PM, local time, for open PRs labeled docs

23Intermediate

PR review prep

Summarizes a pull request you need to review: what changed, what to look at first, and which files are noise.

Dev and coding

GitHub

Weekdays at 9:00 AM, for reviews waiting on you