send-update-email-batchlisted

# Bridge: Send Update Email (Batch) **Announce at start:** "I'm using the bridge:send-update-email-batch skill to send accumulated update emails across this folder's repos." ## Purpose Runs unattended across a parent folder of repos (e.g. scheduled via `/loop`), sending each configured repo's version-grouped, bullet-point update email via its own dedicated Resend MCP connection. This skill shares its core per-repo logic (commit gathering, content filtering, grouping, the email template, the send/state-update mechanics) with `/bridge:send-update-email` — the only real difference is this one never asks for confirmation before sending, since there's no one to ask when it's running unattended, and it processes every repo in the folder instead of just the current one. **When editing the core per-repo logic here, make the same edit in `skills/send-update-email/SKILL.md`** — the two are meant to stay behaviorally identical apart from the confirmation gate and the parent-folder loop. For interactive, single-repo sending with a confirmation step, use `/bridge:send-update-email` instead. ## Requirements - **A dedicated Resend MCP connection per repo**, registered by `/bridge:setup-email-updates`. Each repo's `.bridge/email-config.json` names its own connection via `mcpServerName`. A repo whose connection isn't registered on this machine is skipped (see Step 3's Error Handling below) — this skill never registers connections itself. ## Step 1 — Require Parent-Folder Context ```ba