send-update-emaillisted

# Bridge: Send Update Email **Announce at start:** "I'm using the bridge:send-update-email skill to send an update email for accumulated changes." ## Purpose Sends colleagues a readable, bullet-point update email summarizing everything that changed in this repo since the last successful send, grouped by version and by root cause rather than listed commit-by-commit. Delivered via the Resend MCP server. Always shows you the rendered subject/recipients/body and waits for explicit confirmation before sending anything. This skill only works inside a single repo. For unattended sending across a parent folder of repos (e.g. scheduled via `/loop`), use `/bridge:send-update-email-batch` instead — it shares this skill's core logic (Steps 2-7, 9, 10 below) but skips the confirmation step, since there's no one to ask when it's running unattended. **When editing the core logic here (commit gathering, content filtering, grouping, the email template, or the send/state-update mechanics), make the same edit in `skills/send-update-email-batch/SKILL.md`** — the two are meant to stay behaviorally identical apart from the confirmation gate and the parent-folder loop. ## Requirements - **A dedicated Resend MCP connection for this repo.** This skill never holds a Resend API key or a sender address itself — both live inside a per-repo MCP server (named `resend-<repo-slug>`) that `/bridge:setup-email-updates` registers once, with a fixed `SENDER_EMAIL_ADDRESS` for that repo. `.bridge/email-conf