Generate an English Slack-ready post and save a temporary Markdown copy from an Apache Doris weekly community report MDX file. Use when the user invokes `$weekly-report-slack path/to/report.mdx` or asks to turn a Doris weekly report, especially `src/pages/community-report/_reports/YYYY-MM-DD.mdx`, into the standard Slack announcement format with date range, summary paragraph, highlights, and report link.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
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.
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": { ... } }python3 doc-tools/skills/weekly-report-slack/scripts/generate_slack_post.py <report-path>
.md file, and reports the saved path.python3 doc-tools/skills/weekly-report-slack/scripts/generate_slack_post.py <report-path> --report-link <url>
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]
📝 We’d love your feedback—please fill out our survey:
https://docs.google.com/forms/d/e/1FAIpQLSeSppR5JJyXIxNoPlG_hS8RTW8k2tsCkpC0h68WSN6CEUsWcA/viewform
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.
Always include the survey invitation and URL shown in the template immediately after the report link.
Every run must save the complete post to the temporary Markdown path produced by the script and tell the user that path. Do not include the path inside the Slack post itself.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
Publish a new Apache Doris Core or Doris ecosystem release on the Doris website. Use when updating download data, bilingual release notes, the Doris Core release index, release navigation, or ecosystem release pages. Confirm the component and release metadata first because Core and ecosystem releases use different files and validation paths.
日本語の概要は準備中です。原文の説明を表示しています。
Restructure and SEO/GEO-optimize an existing Apache Doris user documentation file (`.md` / `.mdx`), primarily under `i18n/zh-CN/docusaurus-plugin-content-docs-next/current/` or `docs-next/`. The skill reorganizes the doc from a user-scenario perspective, applies tables and lists for parameters / scenarios / FAQs, fixes formatting (4-space indent, code-block language tags, blank lines, Chinese/English spacing, command-concatenation bugs), validates every external link with `curl` and every `/images/...` reference against `static/`, and updates the frontmatter `description` + `keywords` per the bundled `./references/seo-geo.md` guide — all without changing the original meaning or dropping any technical content (commands, parameters, YAML, sample outputs, images are preserved verbatim). Use this skill whenever the user points at a single Doris doc file and asks to "优化这篇文档", "重新组织这篇文档", "帮我优化文档结构", "对这篇文章进行 SEO 优化", "按 SEO/GEO 优化这篇文档", "调整一下这篇文档的结构", "把这篇文档润色一下", "optimize this doc", "restructure this doc", "polish this doc", or anything similar — even if the user only says "make this doc better" or "这篇文档读起来不顺" while pointing at a Doris doc path. Do NOT use this skill for translating between languages (use `doris-translate-zh-to-en` instead), writing a brand-new doc from scratch (use `doris-feature-card` or `doc-coauthoring`), or pure link-checking without restructure (use `check-md-links` instead).
日本語の概要は準備中です。原文の説明を表示しています。
Create Apache Doris article illustrations in the Doris hand-drawn whiteboard style, using a randomly selected Pip, Dori, or Flux mascot only when a task, guide, operator, diagnosis, or anthropomorphic narrative benefits from a character. Use when the user invokes $doris-img-gen or asks for a Doris technical article illustration, concept visual, infographic, architecture diagram, process diagram, or mascot-assisted explanatory graphic.
日本語の概要は準備中です。原文の説明を表示しています。
Audit and update the user documentation for an Apache Doris release from the commit diff between two refs (for example 4.1.3..4.1.4-rc04). Extract the hard user-facing surface (FE/BE/MS configs, session variables, grammar, functions, system tables, HTTP endpoints, metrics, shipped conf files, dependency versions), classify every commit with parallel subagents, then add, fix or create docs under three iron rules — anything a user can perceive needs a doc, every new feature or behavior change carries a "since version X.Y.Z" note, and every feature commit needs a documented home or a question to the user. Write the Chinese version of ONE doc branch first (ask which one: dev or 4.x), open a PR, and only after the user approves it sync to the other branches and to English (dev documents master, so build a master-vs-tag difference table first). Use when asked to "check the docs for 4.1.5", "update docs from the commit history", "what docs need to change for X.Y.Z", or "sync the 4.x doc changes to dev and English". Not for writing release notes and not for building the site (static checks only).
日本語の概要は準備中です。原文の説明を表示しています。