Weekly Report Slack

Overview

Create a concise English post for Slack from a weekly Apache Doris community report. The output follows the community announcement template and is meant to be pasted directly into Slack.

Input

Require exactly one report path, usually:

$weekly-report-slack src/pages/community-report/_reports/2026-06-29.mdx

If no path is provided, ask for the report path. If multiple paths are provided, ask which single report to convert.

The expected source format is the structured MDX generated by community-radar, with exports such as:

• export const label = "...";
• export const report = { "summary": { ... } }

Workflow

1. Resolve the report path from the repository root.
2. Run the bundled script:

python3 doc-tools/skills/weekly-report-slack/scripts/generate_slack_post.py <report-path>

3. Return the generated Slack post as the main answer. Do not wrap it in a code fence unless the user asks for a fenced block.
4. If the report is unpublished, or the user provides a preview URL, pass it explicitly:

python3 doc-tools/skills/weekly-report-slack/scripts/generate_slack_post.py <report-path> --report-link <url>

Output Rules

Preserve this Slack formatting:

📊 *Apache Doris Weekly Report — [DATE RANGE]*

[One short summary paragraph]

✨ *Highlights*
• [Highlight 1]
• [Highlight 2]
• [Highlight 3]

👉 Read the full weekly report:
[REPORT LINK]

Big thanks to everyone who contributed, reviewed, tested, reported issues, and shared feedback this week! 🙌

Use the report's label as [DATE RANGE], report.summary.lead as the opening summary paragraph, and report.summary.highlights for the highlight bullets unless the user asks for a different tone or length.

By default, the report link is https://doris.apache.org/community-report#<filename-without-extension>, because the website uses URL hashes to deep-link weekly reports.

Guardrails

• Keep the post in English.
• Keep exactly three highlight bullets unless the report has fewer than three highlights.
• Prefer highlight titles over long narratives for the bullets.
• Do not invent numbers, links, or highlights. If a required field is missing, report the missing field and stop.
• Do not edit the source report file.