generate-change-log

Generate change log

Turn commits into a Slack post that marketing, customer service, and sales can read without engineering context.

Default repos:

• API / backend: ~/code/soraban-api
• Frontend / UI: ~/code/soraban-react-app

Treat "api", "backend", "server" as soraban-api, and "frontend", "UI", "web", "react" as soraban-react-app. Other repos are supported — the user just has to say which one, and where it lives on disk.

Required input

One or two commit SHAs. Valid shapes:

• Two SHAs, one per repo (a change that needed both backend and frontend)
• One SHA in either repo (backend-only or frontend-only change)

All SHAs passed in one run describe a single change. Write one entry covering the whole change, never one entry per repo or per commit.

If no SHA was given, stop and ask for one with the AskQuestion tool — one question, options soraban-api, soraban-react-app, both repos, another repo, so the user can answer the repo inline and supply the SHA as free text. Do not guess from recent history and do not pick a recent commit.

Workflow

1. Resolve each SHA to a repo

If the user named a repo, use it. Map "api"/"backend" to ~/code/soraban-api and "frontend"/"UI" to ~/code/soraban-react-app. For any other named repo, use it if it is a git repo under ~/code; if it is not there, ask the user for its path.

Otherwise, try the two defaults:

for r in ~/code/soraban-api ~/code/soraban-react-app; do
  git -C "$r" cat-file -e "<sha>^{commit}" 2>/dev/null && echo "$r"
done

Stop and ask the user with AskQuestion whenever the repo is unclear:

• Resolves in neither default repo — ask which repo it belongs to, offering soraban-api, soraban-react-app, and "another repo (I'll give you the path)". Do not go searching other directories yourself.
• Resolves in both repos — likely a short SHA collision. Ask which one is intended.
• Ambiguous short SHA (git cat-file reports more than one object) — ask for the full SHA.