Digest Ship

If the user provides a specific date or range, use that instead.

Step 2: Fetch merged PRs

Use the shared team-prs script to get all merged PRs filtered to team members:

${CLAUDE_PLUGIN_ROOT}/scripts/team-prs.sh ${TARGET_DATE}

This script automatically fetches team members from GitHub and filters PRs across all repos.

If a repo returns zero team PRs, skip it in the output.

Step 3: Fetch completed Linear tickets

Use Glean to find CDIN tickets completed on the target date:

Tool: mcp__glean_default__search Query: CDIN completed or CDIN done Filters: past day, Linear source

If Glean returns limited results, also try:

Tool: mcp__glean_default__chat Query: "What CDIN Linear tickets were completed yesterday?"

Include ticket titles and links in the output. Linear ticket URLs follow the pattern: https://linear.app/klaviyo/issue/CDIN-{number}

Step 4: Supplementary context (optional)

Use mcp__glean_default__search to look for any Slack announcements about releases, incidents, or notable changes from team members. This enriches the "Risks & Follow-ups" section.

Do not block the digest on this step. If Glean returns nothing useful, skip it.

Output Format

Print the digest in this exact format:

# What We Shipped — {Weekday}, {YYYY-MM-DD}

## Summary
- {bullet 1: most impactful change}
- {bullet 2}
- {bullet 3}
- {up to 5 bullets total}

## Shipped by Repo

### {repo-name}
- **{PR title}** ([#{number}]({url})) — @{author}
- **{PR title}** ([#{number}]({url})) — @{author}

### {repo-name}
- ...

## Completed Tickets
- **{ticket title}** ([CDIN-{number}]({linear_url}))
- **{ticket title}** ([CDIN-{number}]({linear_url}))

## Risks & Follow-ups
- {0-5 bullets highlighting anything that needs monitoring, was reverted, or has open follow-ups}
- If nothing notable: "None identified."

Rules

• Summary bullets should focus on user-facing or system-impact changes, not mechanical refactors (unless that's all that shipped).
• Always include links — PR URLs and Linear ticket URLs.
• Group PRs by repo, not by person.
• If a PR body references a Linear ticket (e.g., CDIN-123), cross-link both.
• If nothing shipped (no PRs, no tickets): output "Nothing shipped on {date}." with a single line.
• If a data source fails (gh CLI auth error, Glean timeout): note the gap in the output rather than failing silently. Example: "(Could not fetch Linear data — Glean search returned no results.)"