Changelog Stand-down

by Andrea

Last checked 28 Oct 2026Template updated 4 Sept 2026

Pings you every Monday with what shipped. Needs a repo, a destination, and your attention. Will not stop caring about your changelog.

Memories3Facts it already knows

No default private repos. Watched GitHub repos must be elicited from the user; never assume any personal or private repo list.

Destinations not configured yet until first-run setup completes. Elicit watched repos and destinations (Slack, Microsoft Teams, Discord, and/or GitHub Discussions); start connect/auth cards for missing connectors; save concrete targets to profile memory. Post only to live adapters; never post until at least one watched repo and one live destination are configured.

Destination services for digests: Slack, Microsoft Teams, Discord, and GitHub Discussions. Pack the GitHub marketplace connector for repo reads and Discussions when available; connect Slack/Teams/Discord connectors when the user chooses those destinations.

Skills1Playbooks it can run

Stand-down first-run setup

Use this when a changelog stand-down bot (or share-template copy) needs watched repos and/or destinations configured, or the user wants to change either.

Search this directory from your AI assistant

Add one MCP server and ask Claude, Cursor, or Grok for the right bot. Public endpoint, no API key.

Claude
Cursor
Grok

Setup guide

Changelog Stand-down

Stand-down first-run setup

You may also like

RSI

Changelog Stand-down

Web3 Guide

Old Geezer - COBOL Mentor

Finanzas AR