chore: sync lark-doc from v47 online-doc - #1800
Closed
liuxin-0319 wants to merge 1 commit into
Closed
Conversation
github-actions
Bot
added
domain/ccm
📝 WalkthroughWalkthroughThis PR adds a Lark Doc writing-types skill library: workflow routing updates, a directory index, and many new markdown skill specifications for copywriting, commentary, planning, official/reflective writing, strategic planning, and script/speech generation, each with Feishu-format rules and sample documents. ChangesWriting-Type Skills Library
Estimated code review effort: 3 (Moderate) | ~25 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🚀 PR Preview Install Guide🧰 CLI updatenpm i -g https://pkg.pr.new/larksuite/cli/@larksuite/cli@2b46d063fb074ad276353fd55e705ecd80575ddf🧩 Skill updatenpx skills add larksuite/cli#chore/sync-lark-doc-from-v47-online-doc -y -g |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1800 +/- ##
=======================================
Coverage 74.43% 74.43%
=======================================
Files 860 860
Lines 89827 89827
=======================================
Hits 66864 66864
Misses 17781 17781
Partials 5182 5182 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
![coderabbitai[bot]](https://avatars.github.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 20
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
skills/lark-doc/writing-types/samples/web-romance-hook2.sample.言情小说导语十四篇.md (1)
1-123: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winTitle/count mismatch: this sample only has 13篇.
The title says “十四篇”, but the body only contains sections
## 1through## 13. Please either add the missing 14th sample or rename the file/title so the reference set stays internally consistent.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@skills/lark-doc/writing-types/samples/web-romance-hook2.sample.言情小说导语十四篇.md` around lines 1 - 123, The sample is inconsistent because the title says “十四篇” but the content only includes entries labeled from ## 1 to ## 13. Update the markdown in this sample by either adding the missing 14th romance hook or changing the title so it matches the actual count, and make sure the heading text and section numbering in web-romance-hook2.sample stay aligned.skills/lark-doc/writing-types/samples/K12-study-plan.sample.K12学习计划3篇.md (1)
11-43: 🎯 Functional Correctness | 🟠 Major | ⚡ Quick winKeep this sample K12-only.
The taxonomy reintroduces university/certification/vocational plans, which conflicts with
K12-study-plan.md's scope guard not to force non-K12 requests into this skill. Trim those categories or move them to a separate generic sample.Suggested trim
-2. **高等与专业课程学习计划** -3. **考试认证备考计划** -4. **职业技能学习计划** -5. **兴趣才艺学习计划** -6. **阅读研修计划** +2. **K12 补充学习计划** + 只保留小学/初中/高中课内相关变体，例如预习、复习、提分、冲刺和假期安排。🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@skills/lark-doc/writing-types/samples/K12-study-plan.sample.K12学习计划3篇.md` around lines 11 - 43, The sample in K12-study-plan should stay strictly K12-focused and not reintroduce non-K12 plan categories. Remove or relocate the entries in the taxonomy that cover higher education, exam certification, vocational skills, and related generic study plans, and keep only K12-aligned categories/examples in this sample. Use the K12-study-plan sample section and its category list as the location to trim the non-K12 content.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@skills/lark-doc/writing-types/culture-review-literary-works.md`:
- Around line 3-21: Move the description and scope in
culture-review-literary-works.md into alignment with the actual guidance: the
current “适用于” text promises film, music, games, exhibitions, animation, and
comics, but the rest of the document only provides literary-text review rules.
Either narrow the description and “适用范围” to文学评论/文本类作品, or add dedicated branches
in the existing review sections for those non-text media, so the symbol set
under “文化作品评论” matches the instructions that follow.
In `@skills/lark-doc/writing-types/event-copy.md`:
- Around line 209-217: The default multi-version policy is inconsistent between
this section and the later fallback rule, so align them to a single source of
truth. Update the guidance in the event-copy policy around the multi-version
output rules so it clearly governs the default count for short and long copy,
and adjust or remove the conflicting fallback in section 15.6 so both references
like “多版本输出模式” and the short-copy/long-copy version limits agree.
- Around line 131-136: The CTA guidance in event-copy.md should not present
urgency or scarcity as a default rule; update the “CTA 结尾” section referenced by
the “行动暗示” bullet so it only recommends urgency when there is a real deadline,
quota, or other factual constraint. Keep the “降低门槛” and “清晰指引” guidance intact,
and adjust the wording to avoid implying fabricated scarcity while preserving
the intended call-to-action behavior.
In `@skills/lark-doc/writing-types/execution-plan.md`:
- Around line 148-175: The shortcut examples still show --api-version v2 even
though it is a hidden compatibility flag, so update the documented commands in
execution-plan.md to remove that flag from the lark-cli docs +create and docs
+update examples. Keep the rest of the workflow intact, and make sure the
surrounding guidance in the same section still matches the commands shown.
In `@skills/lark-doc/writing-types/film-critic.md`:
- Line 129: The citation guidance in the “怎么用” section still uses a hard-coded
placeholder link that will generate unusable citations. Update the wording in
the film-critic writing type doc to reference the actual source URL format used
by the renderer, or describe that the renderer will inject the URL separately;
keep the citation instruction tied to the external-source note so generated
fact-backed reviews produce valid links.
In `@skills/lark-doc/writing-types/news-commentary.md`:
- Around line 271-285:
“整理成文档/评论方案/模板”这类需求与纯正文评论模式冲突：当前格式规范里把有序列表和无序列表一律禁掉，导致提纲和模板无法正常输出。请在
news-commentary.md 中围绕“12.1 输出类型”和“12.2
格式排版要求”做区分，把列表禁令仅保留给新闻评论正文模式，同时在评论提纲、完整评论方案、写作模板等模式下允许使用列表；可通过明确区分
mode/产物类型来调整规则，确保“评论对象、核心观点、事实依据、论证结构、成品、核查项”等内容能用列表清晰呈现。
In `@skills/lark-doc/writing-types/productreview.md`:
- Around line 121-124: The risk bucket list in the product review taxonomy is
combining two unrelated categories, which can misroute prompts. Update the
category definitions in the writing-types logic so “保险” and “收藏” are split into
separate buckets before the classifier consumes them, and make sure any matching
or routing code that references this list uses the individual category names
rather than the combined label.
In `@skills/lark-doc/writing-types/samples/emergency-plan.sample.城市排水防涝应急预案.md`:
- Around line 41-64: The sample outline is no longer aligned with the canonical
10-chapter structure, because it introduces standalone 6/7 chapters and pushes
the later content into 11/12. Update the emergency plan sample so it follows the
standard 10-chapter frame used by this template, keeping the existing content
but renumbering/regrouping sections to fit the canonical structure around the
current chapter headings such as “8.应急响应”, “9.紧急避险”, and “10.信息报送及发布”.
- Around line 33-35: The sample still uses generic placeholders like “相关单位/相关部门”
in the risk and warning sections; replace them with concrete responsible offices
or岗位 names so ownership is explicit. Update the affected entries in the
emergency plan sample to name specific handlers, and make the same style fix
wherever the same placeholder pattern appears in the related risk warning/risk
control content. Use the existing section text around “城区内涝专班”, “风险提示”, and
“风险管控” to locate and replace these references consistently.
In `@skills/lark-doc/writing-types/samples/project-plan.sample.项目计划模板.md`:
- Around line 202-247: The 项目计划模板 in the sample currently uses H4 headings
(####) and exceeds the documented heading ceiling. Update the template to use no
deeper than H3 throughout, keeping the same structure but flattening each
section heading and list block under the appropriate H3 level. Refer to the
template section titles like “项目名称实施计划”, “一、项目背景”, and “七、工作要求” to make the
heading-level adjustment consistently across the sample.
In `@skills/lark-doc/writing-types/samples/short-play-script.sample.短剧第一集参考剧本.md`:
- Line 37: The sample line in the short play script merges Zheng Qi’s narration
and the next spoken line into one entry, violating the per-line dialogue
convention. Split the combined text in the sample so the narration belongs to
the OS turn and the following “郑萋” dialogue appears as its own separate line,
keeping the existing speaker labels and screenplay format consistent.
In `@skills/lark-doc/writing-types/samples/speech-draft.sample.scenarios.md`:
- Around line 44-48: The cross-file reference in the “C2 晚会 / 年会主持串词” section
points to the wrong companion document; update the formats reference so it
targets speech-draft.sample.formats.md instead of formats.md. Use the existing
“主持串词” mention in this scenario entry to locate and fix the link text so readers
can reach the correct template.
In
`@skills/lark-doc/writing-types/samples/strategic-planning.sample.建元信托战略规划纲要.md`:
- Line 25: The strategic-goal phrasing in the planning text is awkward because
it uses “重点完成” for “风险化解”; update the wording in the affected sentence to use
“实现” instead so the goal reads naturally. Keep the rest of the paragraph intact
and adjust only the strategic objective phrasing around “战略目标” and “风险化解”.
In
`@skills/lark-doc/writing-types/samples/strategic-planning.sample.泰晶电子战略规划`（2016年—2020年）.md:
- Line 43: The sample text contains a typo in the strategic planning paragraph:
“人工陈本” should be corrected to “人工成本”. Update the affected sentence in the
markdown sample so the wording is consistent and free of visible errors, keeping
the rest of the content unchanged.
In
`@skills/lark-doc/writing-types/samples/work-summary.sample.华亭市人民政府关于2024年工作总结的报告.md`:
- Line 53: The phrase in the planning-summary sentence uses an awkward
collocation with “目标”; update the wording in the 2025 outlook sentence so it
uses “实现” with the “十四五”规划目标 expression. Locate the long年度目标 paragraph in the
work-summary sample and adjust that specific clause to a more standard summary
phrasing while keeping the rest of the sentence unchanged.
In
`@skills/lark-doc/writing-types/samples/work-summary.sample.苏州市城市管理局2024年上半年工作总结.md`:
- Line 45: The sample text has a malformed quotation mark around 行走苏城 in the
phrase used for the 小程序 reference. Fix the quote pairing in this paragraph so
the opening and closing Chinese quotes match, and verify the same wording stays
consistent with the surrounding “行动方案” reference in this sample document.
- Line 187: The Markdown section in the work-summary sample has the heading and
body merged on one line, so the text after “### （四）开展专项排查整治” is rendered as part
of the heading. Update this sample by separating the heading from its paragraph
content so the body starts on the next line, preserving the intended Markdown
structure.
In `@skills/lark-doc/writing-types/speech-draft.md`:
- Around line 137-145: The “内容库(Content Library)” paragraph has a path mismatch:
it describes the reference materials as living under references/ while the
linked files in the same section are under ./samples/. Update the directory
label in this section to match the actual linked assets, and keep the wording
consistent with the three linked docs so readers can follow the workflow from
the speech-draft guide without being sent to the wrong folder.
In `@skills/lark-doc/writing-types/work-reflection.md`:
- Around line 150-170: The subsection numbering under the student work
reflections outline is inconsistent because these two headings are nested within
the 5.3 section but are labeled as 5.4.1 and 5.4.2. Update the headings for the
two subsections in work-reflection.md to match their parent section by
renumbering them to 5.3.1 and 5.3.2, and keep any downstream references
consistent with the new numbering.
In `@skills/lark-doc/writing-types/work-summary.md`:
- Around line 34-35: The routing in work-summary.md is too broad: the branch in
the political-theory summary currently includes student reading reflections and
literary life reflections that should not map to political-theory content.
Tighten the wording around the related item in the summary so
only党务/团务/政治理论学习心得与汇报类任务 are routed to political-theories-reflection.md, and
move any student读后感、观后感或文学性感悟描述 to the appropriate writing-type branch used by
the README routing index.
---
Outside diff comments:
In `@skills/lark-doc/writing-types/samples/K12-study-plan.sample.K12学习计划3篇.md`:
- Around line 11-43: The sample in K12-study-plan should stay strictly
K12-focused and not reintroduce non-K12 plan categories. Remove or relocate the
entries in the taxonomy that cover higher education, exam certification,
vocational skills, and related generic study plans, and keep only K12-aligned
categories/examples in this sample. Use the K12-study-plan sample section and
its category list as the location to trim the non-K12 content.
In `@skills/lark-doc/writing-types/samples/web-romance-hook2.sample.言情小说导语十四篇.md`:
- Around line 1-123: The sample is inconsistent because the title says “十四篇” but
the content only includes entries labeled from ## 1 to ## 13. Update the
markdown in this sample by either adding the missing 14th romance hook or
changing the title so it matches the actual count, and make sure the heading
text and section numbering in web-romance-hook2.sample stay aligned.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 02f77360-13a7-4c5f-8f2a-3e29a0cd635d
📒 Files selected for processing (45)
skills/lark-doc/references/style/lark-doc-create-workflow.mdskills/lark-doc/references/style/lark-doc-update-workflow.mdskills/lark-doc/writing-types/K12-study-plan.mdskills/lark-doc/writing-types/README.mdskills/lark-doc/writing-types/ad.mdskills/lark-doc/writing-types/culture-review-literary-works.mdskills/lark-doc/writing-types/emergency-plan.mdskills/lark-doc/writing-types/event-copy.mdskills/lark-doc/writing-types/execution-plan.mdskills/lark-doc/writing-types/film-critic.mdskills/lark-doc/writing-types/hotspot-analysis.mdskills/lark-doc/writing-types/marketing-planning.mdskills/lark-doc/writing-types/news-commentary.mdskills/lark-doc/writing-types/political-theories-reflection.mdskills/lark-doc/writing-types/product-seeding-copywriting.mdskills/lark-doc/writing-types/productreview.mdskills/lark-doc/writing-types/project-plan.mdskills/lark-doc/writing-types/samples/K12-study-plan.sample.K12学习计划3篇.mdskills/lark-doc/writing-types/samples/emergency-plan.sample.城市排水防涝应急预案.mdskills/lark-doc/writing-types/samples/event-copy.sample.scenarios.mdskills/lark-doc/writing-types/samples/execution-plan.sample.企业项目上线执行方案.mdskills/lark-doc/writing-types/samples/hotspot-analysis.sample.社会热点分析9篇.mdskills/lark-doc/writing-types/samples/political-theories-reflection.sample.共产党员网.mdskills/lark-doc/writing-types/samples/project-plan.sample.项目计划模板.mdskills/lark-doc/writing-types/samples/short-play-script.sample.短剧第一集参考剧本.mdskills/lark-doc/writing-types/samples/speech-draft.sample.anti-ai.mdskills/lark-doc/writing-types/samples/speech-draft.sample.formats.mdskills/lark-doc/writing-types/samples/speech-draft.sample.scenarios.mdskills/lark-doc/writing-types/samples/strategic-planning.sample.光明乳业股份有限公司2021至2025年战略规划纲要.mdskills/lark-doc/writing-types/samples/strategic-planning.sample.吉大正元公司战略发展规划.mdskills/lark-doc/writing-types/samples/strategic-planning.sample.建元信托战略规划纲要.mdskills/lark-doc/writing-types/samples/strategic-planning.sample.泰晶电子战略规划（2016年—2020年）.mdskills/lark-doc/writing-types/samples/web-romance-hook2.sample.言情小说导语十四篇.mdskills/lark-doc/writing-types/samples/work-summary.sample.华亭市人民政府关于2024年工作总结的报告.mdskills/lark-doc/writing-types/samples/work-summary.sample.安徽省机关事务管理局2023年工作总结.mdskills/lark-doc/writing-types/samples/work-summary.sample.广州工程职业技术学院2024年工作总结.mdskills/lark-doc/writing-types/samples/work-summary.sample.淳安县气象局2024年工作总结及2025年工作计划.mdskills/lark-doc/writing-types/samples/work-summary.sample.苏州市城市管理局2024年上半年工作总结.mdskills/lark-doc/writing-types/short-play-script.mdskills/lark-doc/writing-types/short-video-script.mdskills/lark-doc/writing-types/speech-draft.mdskills/lark-doc/writing-types/strategic-planning.mdskills/lark-doc/writing-types/web-romance-hook2.mdskills/lark-doc/writing-types/work-reflection.mdskills/lark-doc/writing-types/work-summary.md
Comment on lines
+131
to
+136
| ### 7.4 CTA 结尾 | ||
|
|
||
| - **降低门槛**：让用户觉得参与极其简单，毫无心理负担。 | ||
| - **清晰指引**：明确、唯一地告诉用户下一步该怎么做。 | ||
| - **行动暗示**：制造紧迫感或稀缺性（"仅限前50名，送完即止"）。 | ||
|
|
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Keep CTA urgency conditional.
制造紧迫感或稀缺性 reads like a default instruction and conflicts with the earlier ban on虚假稀缺. Please only use urgency when the event really has a deadline or quota.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/lark-doc/writing-types/event-copy.md` around lines 131 - 136, The CTA
guidance in event-copy.md should not present urgency or scarcity as a default
rule; update the “CTA 结尾” section referenced by the “行动暗示” bullet so it only
recommends urgency when there is a real deadline, quota, or other factual
constraint. Keep the “降低门槛” and “清晰指引” guidance intact, and adjust the wording
to avoid implying fabricated scarcity while preserving the intended
call-to-action behavior.
Comment on lines
+209
to
+217
| 除非用户明确且严格地限制【只能输出一个版本】（例如强调“只要1个”、“禁止输出多个”、“不要写多个版本”），否则默认开启多版本输出模式。 | ||
| 准确数量需求仅指用户明确要求“给我3个/4个/5个版本”“输出2版”“生成6条”等数字型交付数量；“一个活动”“一个文案”“一段话”不属于准确数量需求。 | ||
|
|
||
| **特别注意**：用户日常口语表达中的量词或虚词指令（如“**写一个**文案”、“**来个**朋友圈通知”、“帮我**写一段**”）**不构成严格的数量限制**。在此类未明确禁止的情况下，仍需默认触发多版本创作，为用户提供丰富的选择。 | ||
|
|
||
| 在多版本输出模式下，遵循以下数量规范： | ||
| - 朋友圈、社群、活动海报等不超过 300 字的短文案场景，优先输出 5-10 个版本。 | ||
| - 小红书、公众号、口播稿等偏长文案，最多不超过 5 个版本。 | ||
|
|
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Unify the default version policy.
This section asks for 5-10 versions on short copy, but section 15.6 later falls back to 1-3 versions. The skill will produce inconsistent output counts until one rule is removed or made conditional.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~210-~210: 数词与名词之间一般应存在量词，可能缺少量词。
Context: ...多版本输出模式。 准确数量需求仅指用户明确要求“给我3个/4个/5个版本”“输出2版”“生成6条”等数字型交付数量；“一个活动”“一个文案”“一段话”不属于准确数量...
(wa5)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/lark-doc/writing-types/event-copy.md` around lines 209 - 217, The
default multi-version policy is inconsistent between this section and the later
fallback rule, so align them to a single source of truth. Update the guidance in
the event-copy policy around the multi-version output rules so it clearly
governs the default count for short and long copy, and adjust or remove the
conflicting fallback in section 15.6 so both references like “多版本输出模式” and the
short-copy/long-copy version limits agree.
Comment on lines
+148
to
+175
| **前置**：首次使用先 `lark-cli auth login`；所有命令默认 `--as user`、`--api-version v2`。 | ||
|
|
||
| **短方案（≤ 一屏）一次性创建**： | ||
|
|
||
| ```bash | ||
| lark-cli docs +create --api-version v2 \ | ||
| --content @plan.xml | ||
| ``` | ||
|
|
||
| `plan.xml` 内容形如： | ||
|
|
||
| ```xml | ||
| <title>云盾产品上线执行方案</title> | ||
| <h1>1.项目目标</h1> | ||
| <p>本方案围绕功能冻结、公测发布和正式上线三段推进，先收口范围，再压实责任，最后完成灰度与全量发布。</p> | ||
| <h2>1.1总体目标</h2> | ||
| <p>...</p> | ||
| ``` | ||
|
|
||
| **长方案：先建骨架，再分章 `block_insert_after` 填充**（避免一次性 `--content` 触发参数限制）： | ||
|
|
||
| ```bash | ||
| # 1. 建骨架：title + 各级 heading + 简短占位 | ||
| lark-cli docs +create --api-version v2 --content @skeleton.xml | ||
| # 2. 拿到 doc_id 与各 heading block_id 后，逐章追加正文 | ||
| lark-cli docs +update --api-version v2 --doc <doc_id> \ | ||
| --command block_insert_after --block-id <h1_block_id> \ | ||
| --content @section_1.xml |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
rg -n -- '--api-version v2|docs \+fetch|docs \+create|docs \+update' skills/lark-doc/writing-typesRepository: larksuite/cli
Length of output: 2038
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Locate the docs command implementation and related help text/docs.
git ls-files | rg '(^|/)(docs|doc).*(\.go|\.ts|\.js|\.md)$|^README\.md$|^docs/'Repository: larksuite/cli
Length of output: 1768
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Map the relevant files, then read the command implementations and any help text.
ast-grep outline shortcuts/doc/docs_create_v2.go
ast-grep outline shortcuts/doc/docs_fetch_v2.go
ast-grep outline shortcuts/doc/docs_update_v2.go
ast-grep outline shortcuts/doc/v2_only.go
printf '\n--- docs_create_v2.go ---\n'
sed -n '1,220p' shortcuts/doc/docs_create_v2.go
printf '\n--- docs_fetch_v2.go ---\n'
sed -n '1,220p' shortcuts/doc/docs_fetch_v2.go
printf '\n--- docs_update_v2.go ---\n'
sed -n '1,240p' shortcuts/doc/docs_update_v2.go
printf '\n--- v2_only.go ---\n'
sed -n '1,220p' shortcuts/doc/v2_only.goRepository: larksuite/cli
Length of output: 30676
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Find every place docs shortcuts still wire in the compatibility flag and any tests around it.
rg -n -- 'docsAPIVersionCompatFlag|api-version|ignored by docs shortcuts|v2-only' shortcuts/doc tests/cli_e2e/docsRepository: larksuite/cli
Length of output: 4775
Drop --api-version v2 from these examples. The docs shortcuts treat it as a hidden compatibility flag, so keeping it here makes the invocation look required when it isn’t.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/lark-doc/writing-types/execution-plan.md` around lines 148 - 175, The
shortcut examples still show --api-version v2 even though it is a hidden
compatibility flag, so update the documented commands in execution-plan.md to
remove that flag from the lark-cli docs +create and docs +update examples. Keep
the rest of the workflow intact, and make sure the surrounding guidance in the
same section still matches the commands shown.
|
|
||
| 2. **搜什么**：按已锁定的唯一主轴聚焦检索 —— 视听主轴搜摄影 / 美术风格，叙事主轴搜结构特点，类型主轴搜类型定位，社会议题主轴搜现实背景；组合 "片名 + 导演 / 摄影 / 主题 / 风格" 等检索。不为无关维度浪费检索。 | ||
|
|
||
| 3. **怎么用**：只采用可靠信息作论据；并行多条检索交叉印证；引用外部来源支撑事实性描述时按行内 [[标题]](https://mira.bytedance.com/chat/url) 句末标注。 |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Replace the hard-coded citation placeholder.
The current citation target will render dead links in every fact-backed review. Use a real source URL placeholder (or let the renderer inject the URL elsewhere) so generated citations stay usable.
🔧 Proposed fix
-引用外部来源支撑事实性描述时按行内 [[标题]](https://mira.bytedance.com/chat/url) 句末标注。
+引用外部来源支撑事实性描述时按行内 [[标题]](真实来源URL) 句末标注。🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/lark-doc/writing-types/film-critic.md` at line 129, The citation
guidance in the “怎么用” section still uses a hard-coded placeholder link that will
generate unusable citations. Update the wording in the film-critic writing type
doc to reference the actual source URL format used by the renderer, or describe
that the renderer will inject the URL separately; keep the citation instruction
tied to the external-source note so generated fact-backed reviews produce valid
links.
|
|
||
| \### （二）开展“行走苏城” | ||
|
|
||
| 行动出台《“行走苏城”行动方案》，聚焦影响城市品质形象的各个角落环节，鼓励全市城管系统干部职工带头深入基层和网格，积极主动参与城市体检。活动开展以来，行走苏城”小程序累计注册用户 2267 人，巡查里程 8.4 万公里，上报问题1.6万件。相关工作获市委肯定。 |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Fix the broken quote in “行走苏城”.
行走苏城”小程序 is missing the opening Chinese quote, which makes the sample visibly malformed and easy to copy forward as-is.
Proposed fix
-活动开展以来，行走苏城”小程序累计注册用户 2267 人，巡查里程 8.4 万公里，上报问题1.6万件。
+活动开展以来，“行走苏城”小程序累计注册用户 2267 人，巡查里程 8.4 万公里，上报问题 1.6 万件。📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| 行动出台《“行走苏城”行动方案》，聚焦影响城市品质形象的各个角落环节，鼓励全市城管系统干部职工带头深入基层和网格，积极主动参与城市体检。活动开展以来，行走苏城”小程序累计注册用户 2267 人，巡查里程 8.4 万公里，上报问题1.6万件。相关工作获市委肯定。 | |
| 行动出台《“行走苏城”行动方案》，聚焦影响城市品质形象的各个角落环节，鼓励全市城管系统干部职工带头深入基层和网格，积极主动参与城市体检。活动开展以来，“行走苏城”小程序累计注册用户 2267 人，巡查里程 8.4 万公里，上报问题 1.6 万件。相关工作获市委肯定。 |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In
`@skills/lark-doc/writing-types/samples/work-summary.sample.苏州市城市管理局2024年上半年工作总结.md`
at line 45, The sample text has a malformed quotation mark around 行走苏城 in the
phrase used for the 小程序 reference. Fix the quote pairing in this paragraph so
the opening and closing Chinese quotes match, and verify the same wording stays
consistent with the surrounding “行动方案” reference in this sample document.
|
|
||
|
|
||
|
|
||
| \### （四）开展专项排查整治 紧盯城管领域各行业各领域，围绕极端天气、消防安全等，开展排查整治，逐一销号，确保安全。制定雨雪冰冻天气应急工作方案，下发做好环卫行业低温雨雪冰冻天气防范应对工作的提示，最大限度减少极端天气影响。开展消防安全排查，累计发现隐患问题 1256 起，均闭环处置，确保安全无虞。 |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Split the heading and body onto separate lines.
### （四）开展专项排查整治 and the following sentence are on the same line, so Markdown will render the whole sentence as part of the heading. Put the paragraph on the next line to preserve the intended structure.
Proposed fix
-### （四）开展专项排查整治 紧盯城管领域各行业各领域，围绕极端天气、消防安全等，开展排查整治，逐一销号，确保安全。
+### （四）开展专项排查整治
+紧盯城管领域各行业各领域，围绕极端天气、消防安全等，开展排查整治，逐一销号，确保安全。📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| \### （四）开展专项排查整治 紧盯城管领域各行业各领域，围绕极端天气、消防安全等，开展排查整治，逐一销号，确保安全。制定雨雪冰冻天气应急工作方案，下发做好环卫行业低温雨雪冰冻天气防范应对工作的提示，最大限度减少极端天气影响。开展消防安全排查，累计发现隐患问题 1256 起，均闭环处置，确保安全无虞。 | |
| ### （四）开展专项排查整治 | |
| 紧盯城管领域各行业各领域，围绕极端天气、消防安全等，开展排查整治，逐一销号，确保安全。制定雨雪冰冻天气应急工作方案，下发做好环卫行业低温雨雪冰冻天气防范应对工作的提示，最大限度减少极端天气影响。开展消防安全排查，累计发现隐患问题 1256 起，均闭环处置，确保安全无虞。 |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In
`@skills/lark-doc/writing-types/samples/work-summary.sample.苏州市城市管理局2024年上半年工作总结.md`
at line 187, The Markdown section in the work-summary sample has the heading and
body merged on one line, so the text after “### （四）开展专项排查整治” is rendered as part
of the heading. Update this sample by separating the heading from its paragraph
content so the body starts on the next line, preserving the intended Markdown
structure.
Comment on lines
+137
to
+145
| ## 内容库(Content Library) | ||
|
|
||
| 主文件定义目标、边界、流程和约束;具体的、分场景的写作知识沉淀在 `references/` 下,按工作流顺序调用: | ||
|
|
||
| `./samples/speech-draft.sample.scenarios.md` —— 场景库。 两种笔法下细分的具体场景(路演、带货、婚礼、毕业、悼词……),每个场景写明听众特征、语态、默认篇幅、结构模板、踩雷点。**第一步定标后、第三步取料前先读它,精准定位场景。** | ||
|
|
||
| `./samples/speech-draft.sample.formats.md` —— 格式库。 每种讲稿的输出格式骨架(标准致辞、主持串词、路演口播、带货话术、悼词、婚礼祝酒……)。**第三步取料时读它套版。** | ||
|
|
||
| `./samples/speech-draft.sample.anti-ai.md` —— 去 AI 化技法库。 把僵硬书面文字改造成有人味、有呼吸、像真人说话的全套技法(AI 味黑名单、长句剁短、说人话五动作、Show Don't Tell、节奏留白、人设校验)。**第四步清洗时对照它逐项排查。** |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Align the directory label with the linked files.
This paragraph says the scene library lives under references/, but the linked assets below are in ./samples/. That mismatch will send readers to the wrong place.
♻️ Proposed fix
-主文件定义目标、边界、流程和约束;具体的、分场景的写作知识沉淀在 `references/` 下,按工作流顺序调用:
+主文件定义目标、边界、流程和约束;具体的、分场景的写作知识沉淀在 `samples/` 下,按工作流顺序调用:📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| ## 内容库(Content Library) | |
| 主文件定义目标、边界、流程和约束;具体的、分场景的写作知识沉淀在 `references/` 下,按工作流顺序调用: | |
| `./samples/speech-draft.sample.scenarios.md` —— 场景库。 两种笔法下细分的具体场景(路演、带货、婚礼、毕业、悼词……),每个场景写明听众特征、语态、默认篇幅、结构模板、踩雷点。**第一步定标后、第三步取料前先读它,精准定位场景。** | |
| `./samples/speech-draft.sample.formats.md` —— 格式库。 每种讲稿的输出格式骨架(标准致辞、主持串词、路演口播、带货话术、悼词、婚礼祝酒……)。**第三步取料时读它套版。** | |
| `./samples/speech-draft.sample.anti-ai.md` —— 去 AI 化技法库。 把僵硬书面文字改造成有人味、有呼吸、像真人说话的全套技法(AI 味黑名单、长句剁短、说人话五动作、Show Don't Tell、节奏留白、人设校验)。**第四步清洗时对照它逐项排查。** | |
| ## 内容库(Content Library) | |
| 主文件定义目标、边界、流程和约束;具体的、分场景的写作知识沉淀在 `samples/` 下,按工作流顺序调用: | |
| `./samples/speech-draft.sample.scenarios.md` —— 场景库。 两种笔法下细分的具体场景(路演、带货、婚礼、毕业、悼词……),每个场景写明听众特征、语态、默认篇幅、结构模板、踩雷点。**第一步定标后、第三步取料前先读它,精准定位场景。** | |
| `./samples/speech-draft.sample.formats.md` —— 格式库。 每种讲稿的输出格式骨架(标准致辞、主持串词、路演口播、带货话术、悼词、婚礼祝酒……)。**第三步取料时读它套版。** | |
| `./samples/speech-draft.sample.anti-ai.md` —— 去 AI 化技法库。 把僵硬书面文字改造成有人味、有呼吸、像真人说话的全套技法(AI 味黑名单、长句剁短、说人话五动作、Show Don't Tell、节奏留白、人设校验)。**第四步清洗时对照它逐项排查。** |
🧰 Tools
🪛 LanguageTool
[uncategorized] ~145-~145: 数词与名词之间一般应存在量词，可能缺少量词。
Context: ...文字改造成有人味、有呼吸、像真人说话的全套技法(AI 味黑名单、长句剁短、说人话五动作、Show Don't Tell、节奏留白、人设校验)。**第四步清洗时对照它逐...
(wa5)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/lark-doc/writing-types/speech-draft.md` around lines 137 - 145, The
“内容库(Content Library)” paragraph has a path mismatch: it describes the reference
materials as living under references/ while the linked files in the same section
are under ./samples/. Update the directory label in this section to match the
actual linked assets, and keep the wording consistent with the three linked docs
so readers can follow the workflow from the speech-draft guide without being
sent to the wrong folder.
Comment on lines
+150
to
+170
| #### 5.4.1. 实习工作类 | ||
| 实习工作心得体会材料在内容上可能涉及业务学习类和工作总结类中的任意一类，要参考这些类别的要求，同时做到契合学生特点、符合学段特征，包括： | ||
| - 要首先论述形成了对行业的初步总体认知； | ||
| - 要能以小见大写出一些对从事工作的认识，可以展现一定的认识深度； | ||
| - 要体现出用户对行业的兴趣，并简要阐述个人在此行业未来发展的志向； | ||
| - 要体现学校所学专业知识在行业中的运用，并务必结合实例说明； | ||
| - 不得出现写作主体从事某类全职工作的表述； | ||
| - 写作主体是本科一至三年级学生的，不得出现"全职实习"类表述； | ||
| - 不得出现升职、申请晋升等表述，但可以出现申请转正的表达； | ||
| - 工作量应与实习时长相匹配； | ||
| - 不得违背学习、实习的自然规律和能力界限，如出现"完全掌握""彻底弄通""完全能够独当一面"等超出实习生水平的过于夸张的表达。 | ||
|
|
||
| #### 5.4.2. 社会活动类 | ||
| 社会活动心得体会类材料，指的是学生参与公益性社会服务、志愿活动后写作的心得体会，不包括在职场参与实习工作的内容，具体要求包括： | ||
| - 要多从价值观层面写本人的感悟； | ||
| - 要结合具体活动的内容，可以适当用有文采的方式展开描述； | ||
| - 适当结合本人所学专业和兴趣爱好进行论述； | ||
| - 可以将个人的具体活动同国家发展、社会进步及最高领导人对青年的期望等结合起来； | ||
| - 不得明显超出学生课余时间承受水平； | ||
| - 不得出现涉及经济性收益的内容。 | ||
|
|
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Fix the subsection numbering.
5.4.1/5.4.2 sit under 5.3 学生工作心得类, so the outline skips a level and makes the section references inconsistent. Renumber these to 5.3.1/5.3.2.
♻️ Proposed fix
-#### 5.4.1. 实习工作类
+#### 5.3.1. 实习工作类
@@
-#### 5.4.2. 社会活动类
+#### 5.3.2. 社会活动类📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| #### 5.4.1. 实习工作类 | |
| 实习工作心得体会材料在内容上可能涉及业务学习类和工作总结类中的任意一类，要参考这些类别的要求，同时做到契合学生特点、符合学段特征，包括： | |
| - 要首先论述形成了对行业的初步总体认知； | |
| - 要能以小见大写出一些对从事工作的认识，可以展现一定的认识深度； | |
| - 要体现出用户对行业的兴趣，并简要阐述个人在此行业未来发展的志向； | |
| - 要体现学校所学专业知识在行业中的运用，并务必结合实例说明； | |
| - 不得出现写作主体从事某类全职工作的表述； | |
| - 写作主体是本科一至三年级学生的，不得出现"全职实习"类表述； | |
| - 不得出现升职、申请晋升等表述，但可以出现申请转正的表达； | |
| - 工作量应与实习时长相匹配； | |
| - 不得违背学习、实习的自然规律和能力界限，如出现"完全掌握""彻底弄通""完全能够独当一面"等超出实习生水平的过于夸张的表达。 | |
| #### 5.4.2. 社会活动类 | |
| 社会活动心得体会类材料，指的是学生参与公益性社会服务、志愿活动后写作的心得体会，不包括在职场参与实习工作的内容，具体要求包括： | |
| - 要多从价值观层面写本人的感悟； | |
| - 要结合具体活动的内容，可以适当用有文采的方式展开描述； | |
| - 适当结合本人所学专业和兴趣爱好进行论述； | |
| - 可以将个人的具体活动同国家发展、社会进步及最高领导人对青年的期望等结合起来； | |
| - 不得明显超出学生课余时间承受水平； | |
| - 不得出现涉及经济性收益的内容。 | |
| #### 5.3.1. 实习工作类 | |
| 实习工作心得体会材料在内容上可能涉及业务学习类和工作总结类中的任意一类，要参考这些类别的要求，同时做到契合学生特点、符合学段特征，包括： | |
| - 要首先论述形成了对行业的初步总体认知； | |
| - 要能以小见大写出一些对从事工作的认识，可以展现一定的认识深度； | |
| - 要体现出用户对行业的兴趣，并简要阐述个人在此行业未来发展的志向； | |
| - 要体现学校所学专业知识在行业中的运用，并务必结合实例说明； | |
| - 不得出现写作主体从事某类全职工作的表述； | |
| - 写作主体是本科一至三年级学生的，不得出现"全职实习"类表述； | |
| - 不得出现升职、申请晋升等表述，但可以出现申请转正的表达； | |
| - 工作量应与实习时长相匹配； | |
| - 不得违背学习、实习的自然规律和能力界限，如出现"完全掌握""彻底弄通""完全能够独当一面"等超出实习生水平的过于夸张的表达。 | |
| #### 5.3.2. 社会活动类 | |
| 社会活动心得体会类材料，指的是学生参与公益性社会服务、志愿活动后写作的心得体会，不包括在职场参与实习工作的内容，具体要求包括： | |
| - 要多从价值观层面写本人的感悟； | |
| - 要结合具体活动的内容，可以适当用有文采的方式展开描述； | |
| - 适当结合本人所学专业和兴趣爱好进行论述； | |
| - 可以将个人的具体活动同国家发展、社会进步及最高领导人对青年的期望等结合起来； | |
| - 不得明显超出学生课余时间承受水平； | |
| - 不得出现涉及经济性收益的内容。 |
🧰 Tools
🪛 LanguageTool
[uncategorized] ~153-~153: 动词的修饰一般为‘形容词（副词）+地+动词’。您的意思是否是：一定"地"认识
Context: ...了对行业的初步总体认知； - 要能以小见大写出一些对从事工作的认识，可以展现一定的认识深度； - 要体现出用户对行业的兴趣，并简要阐述个人在此行业未来发展的志向；...
(wb4)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/lark-doc/writing-types/work-reflection.md` around lines 150 - 170, The
subsection numbering under the student work reflections outline is inconsistent
because these two headings are nested within the 5.3 section but are labeled as
5.4.1 and 5.4.2. Update the headings for the two subsections in
work-reflection.md to match their parent section by renumbering them to 5.3.1
and 5.3.2, and keep any downstream references consistent with the new numbering.
liuxin-0319
force-pushed
the
chore/sync-lark-doc-from-v47-online-doc
branch
from
July 8, 2026 08:42
1d81725 to
f4e2c69
Compare
There was a problem hiding this comment.
Actionable comments posted: 7
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
skills/lark-doc/writing-types/samples/web-romance-hook2.sample.言情小说导语十四篇.md (1)
1-123: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winMatch the count in the title.
The file promises fourteen hooks, but there are only 13 numbered sections. Either add the missing 14th entry or rename the sample/title to match the actual count.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@skills/lark-doc/writing-types/samples/web-romance-hook2.sample.言情小说导语十四篇.md` around lines 1 - 123, The sample title says there are fourteen hooks, but the content only contains 13 numbered sections. Update the document so the count matches by either adding a new 14th hook or renaming the title to reflect the actual total; use the existing section numbering pattern in the `## 1` through `## 13` entries to locate where to extend the list.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@skills/lark-doc/writing-types/ad.md`:
- Around line 330-340: The section heading in the writing-types doc is
unfinished because it ends with a dangling slash. Update the heading under the
“场景 E：电商卖点 / 种草文案” entry so it reads cleanly, either by removing the trailing
slash or by completing the intended category name, and keep the rest of the
section content unchanged.
In `@skills/lark-doc/writing-types/samples/emergency-plan.sample.城市排水防涝应急预案.md`:
- Line 77: There is a duplicated word in the cited policy title within the
preface paragraph of the emergency plan sample. Update the reference in the long
“依据…” list so the title currently written as “河南省防汛应急应急预案” is corrected to
“河南省防汛应急预案”, keeping the rest of the cited document names unchanged.
- Line 96: The member list entry currently merges two separate roles into one
line, which makes the ownership structure hard to read. In the emergency plan
sample, split the text in the affected member entry so the “专班成员（县气象局副局长）”
responsibility and the “专班成员（柏城、柏亭、柏苑办事处副主任）” responsibility are placed on
separate lines, preserving the same wording but improving readability and
alignment with the rest of the list.
In `@skills/lark-doc/writing-types/samples/hotspot-analysis.sample.社会热点分析9篇.md`:
- Line 70: The paragraph contains an incorrect stray reference to “连云港夫妇” that
conflicts with the surrounding discussion of 陈秀凤/“鹅腿阿姨”. Update the text in this
hotspot-analysis sample so the media narrative only refers to the actual subject
of the article, and remove or replace the copied phrase with the correct entity
name while keeping the sentence flow intact.
In `@skills/lark-doc/writing-types/samples/speech-draft.sample.anti-ai.md`:
- Around line 81-84: Remove the empty blockquoted line in the sample by updating
the quoted example around the speech draft content so there are no blank “>”
lines between the quoted sentences. Keep the surrounding examples intact and
ensure the markdown in speech-draft.sample.anti-ai.md no longer triggers
markdownlint no-blanks-blockquote.
In `@skills/lark-doc/writing-types/strategic-planning.md`:
- Line 71: The small-business guidance in the strategic-planning doc is too
aggressive because “可忽略上述结构” removes the existing strategic scaffold entirely.
Update the wording in the branch for 个体工商户和创业者 so it preserves the
environment/target/path/guardrails framework from the main structure, but
compresses it into a shorter, more practical format focused on short-term
problem solving and execution. Keep the same intent in the strategic-planning
section while ensuring the content still reads as a strategic plan rather than a
pure execution brief.
In `@skills/lark-doc/writing-types/work-reflection.md`:
- Line 55: The route label in the work-reflection guidance is mismatched with
the target link, and the phrase “生活感悟感悟” contains a duplicated word. Update the
visible link text in the sentence around the
`思想汇报`/`political-theories-reflection` reference so it matches the actual linked
document name, and revise the “生活感悟感悟” wording to a single, correct term while
keeping the meaning unchanged.
---
Outside diff comments:
In `@skills/lark-doc/writing-types/samples/web-romance-hook2.sample.言情小说导语十四篇.md`:
- Around line 1-123: The sample title says there are fourteen hooks, but the
content only contains 13 numbered sections. Update the document so the count
matches by either adding a new 14th hook or renaming the title to reflect the
actual total; use the existing section numbering pattern in the `## 1` through
`## 13` entries to locate where to extend the list.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: d95164e5-2e8a-4955-8dc2-b52f21f48b56
📒 Files selected for processing (45)
skills/lark-doc/references/style/lark-doc-create-workflow.mdskills/lark-doc/references/style/lark-doc-update-workflow.mdskills/lark-doc/writing-types/K12-study-plan.mdskills/lark-doc/writing-types/README.mdskills/lark-doc/writing-types/ad.mdskills/lark-doc/writing-types/culture-review-literary-works.mdskills/lark-doc/writing-types/emergency-plan.mdskills/lark-doc/writing-types/event-copy.mdskills/lark-doc/writing-types/execution-plan.mdskills/lark-doc/writing-types/film-critic.mdskills/lark-doc/writing-types/hotspot-analysis.mdskills/lark-doc/writing-types/marketing-planning.mdskills/lark-doc/writing-types/news-commentary.mdskills/lark-doc/writing-types/political-theories-reflection.mdskills/lark-doc/writing-types/product-seeding-copywriting.mdskills/lark-doc/writing-types/productreview.mdskills/lark-doc/writing-types/project-plan.mdskills/lark-doc/writing-types/samples/K12-study-plan.sample.K12学习计划3篇.mdskills/lark-doc/writing-types/samples/emergency-plan.sample.城市排水防涝应急预案.mdskills/lark-doc/writing-types/samples/event-copy.sample.scenarios.mdskills/lark-doc/writing-types/samples/execution-plan.sample.企业项目上线执行方案.mdskills/lark-doc/writing-types/samples/hotspot-analysis.sample.社会热点分析9篇.mdskills/lark-doc/writing-types/samples/political-theories-reflection.sample.共产党员网.mdskills/lark-doc/writing-types/samples/project-plan.sample.项目计划模板.mdskills/lark-doc/writing-types/samples/short-play-script.sample.短剧第一集参考剧本.mdskills/lark-doc/writing-types/samples/speech-draft.sample.anti-ai.mdskills/lark-doc/writing-types/samples/speech-draft.sample.formats.mdskills/lark-doc/writing-types/samples/speech-draft.sample.scenarios.mdskills/lark-doc/writing-types/samples/strategic-planning.sample.光明乳业股份有限公司2021至2025年战略规划纲要.mdskills/lark-doc/writing-types/samples/strategic-planning.sample.吉大正元公司战略发展规划.mdskills/lark-doc/writing-types/samples/strategic-planning.sample.建元信托战略规划纲要.mdskills/lark-doc/writing-types/samples/strategic-planning.sample.泰晶电子战略规划（2016年—2020年）.mdskills/lark-doc/writing-types/samples/web-romance-hook2.sample.言情小说导语十四篇.mdskills/lark-doc/writing-types/samples/work-summary.sample.华亭市人民政府关于2024年工作总结的报告.mdskills/lark-doc/writing-types/samples/work-summary.sample.安徽省机关事务管理局2023年工作总结.mdskills/lark-doc/writing-types/samples/work-summary.sample.广州工程职业技术学院2024年工作总结.mdskills/lark-doc/writing-types/samples/work-summary.sample.淳安县气象局2024年工作总结及2025年工作计划.mdskills/lark-doc/writing-types/samples/work-summary.sample.苏州市城市管理局2024年上半年工作总结.mdskills/lark-doc/writing-types/short-play-script.mdskills/lark-doc/writing-types/short-video-script.mdskills/lark-doc/writing-types/speech-draft.mdskills/lark-doc/writing-types/strategic-planning.mdskills/lark-doc/writing-types/web-romance-hook2.mdskills/lark-doc/writing-types/work-reflection.mdskills/lark-doc/writing-types/work-summary.md
✅ Files skipped from review due to trivial changes (5)
- skills/lark-doc/writing-types/samples/short-play-script.sample.短剧第一集参考剧本.md
- skills/lark-doc/writing-types/README.md
- skills/lark-doc/writing-types/samples/strategic-planning.sample.泰晶电子战略规划（2016年—2020年）.md
- skills/lark-doc/references/style/lark-doc-update-workflow.md
- skills/lark-doc/writing-types/work-summary.md
🚧 Files skipped from review as they are similar to previous changes (2)
- skills/lark-doc/references/style/lark-doc-create-workflow.md
- skills/lark-doc/writing-types/marketing-planning.md
Comment on lines
+330
to
+340
| ### 场景 E：电商卖点 / 种草文案 / | ||
|
|
||
| 策略：先抓住真实需求，再给出具体理由。 | ||
|
|
||
| 要求： | ||
|
|
||
| - 要有明确使用场景、真实痛点、具体好处和行动理由。 | ||
| - 语言可以更亲近，但不能像硬广模板。 | ||
| - 电商卖点要有购买理由。 | ||
| - 种草文案要像真实体验，而不是品牌自夸。 | ||
|
|
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Complete the section heading.
### 场景 E：电商卖点 / 种草文案 / ends with a dangling slash and looks unfinished. Drop it or rename the branch so the outline reads cleanly.
♻️ Proposed fix
-### 场景 E：电商卖点 / 种草文案 /
+### 场景 E：电商卖点 / 种草文案📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| ### 场景 E：电商卖点 / 种草文案 / | |
| 策略：先抓住真实需求，再给出具体理由。 | |
| 要求： | |
| - 要有明确使用场景、真实痛点、具体好处和行动理由。 | |
| - 语言可以更亲近，但不能像硬广模板。 | |
| - 电商卖点要有购买理由。 | |
| - 种草文案要像真实体验，而不是品牌自夸。 | |
| ### 场景 E：电商卖点 / 种草文案 | |
| 策略：先抓住真实需求，再给出具体理由。 | |
| 要求： | |
| - 要有明确使用场景、真实痛点、具体好处和行动理由。 | |
| - 语言可以更亲近，但不能像硬广模板。 | |
| - 电商卖点要有购买理由。 | |
| - 种草文案要像真实体验，而不是品牌自夸。 |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/lark-doc/writing-types/ad.md` around lines 330 - 340, The section
heading in the writing-types doc is unfinished because it ends with a dangling
slash. Update the heading under the “场景 E：电商卖点 / 种草文案” entry so it reads
cleanly, either by removing the trailing slash or by completing the intended
category name, and keep the rest of the section content unchanged.
| 1.1指导思想 | ||
| 为切实做好城市排水防涝和城市内涝灾害的预防和应急处置，保证城市排水防涝和内涝抢险救灾工作科学高效有序进行，有效防止和减轻城市内涝灾害，最大程度避免人员伤亡和减少财产损失，为城市安全运行、促进社会稳定提供有力的支持和保障，结合本地实际情况制定本预案。 | ||
| 1.2编制依据 | ||
| 依据《中华人民共和国突发事件应对法》《中华人民共和国防洪法》《中华人民共和国防汛条例》《气象灾害防御条例》《城镇排水与污水处理条例》《河南省实施〈中华人民共和国防洪法〉办法》《河南省气象灾害防御条例》《河南省气象灾害预警信号发布与传播办法》《河南省政府关于改革完善应急管理体系的通知》《国家自然灾害救助应急预案》《河南省突发事件总体应急预案（试行）》《河南省自然灾害救助应急预案》《河南省救灾物资储备管理暂行办法》《河南省防汛应急应急预案》《河南省城市排水防涝应急预案》、《驻马店市防汛应急预案》等，制定本预案。 |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Fix the duplicated word in the cited title.
河南省防汛应急应急预案 should read 河南省防汛应急预案.
♻️ Proposed fix
-《河南省防汛应急应急预案》
+《河南省防汛应急预案》📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| 依据《中华人民共和国突发事件应对法》《中华人民共和国防洪法》《中华人民共和国防汛条例》《气象灾害防御条例》《城镇排水与污水处理条例》《河南省实施〈中华人民共和国防洪法〉办法》《河南省气象灾害防御条例》《河南省气象灾害预警信号发布与传播办法》《河南省政府关于改革完善应急管理体系的通知》《国家自然灾害救助应急预案》《河南省突发事件总体应急预案（试行）》《河南省自然灾害救助应急预案》《河南省救灾物资储备管理暂行办法》《河南省防汛应急应急预案》《河南省城市排水防涝应急预案》、《驻马店市防汛应急预案》等，制定本预案。 | |
| 依据《中华人民共和国突发事件应对法》《中华人民共和国防洪法》《中华人民共和国防汛条例》《气象灾害防御条例》《城镇排水与污水处理条例》《河南省实施〈中华人民共和国防洪法〉办法》《河南省气象灾害防御条例》《河南省气象灾害预警信号发布与传播办法》《河南省政府关于改革完善应急管理体系的通知》《国家自然灾害救助应急预案》《河南省突发事件总体应急预案（试行）》《河南省自然灾害救助应急预案》《河南省救灾物资储备管理暂行办法》《河南省防汛应急预案》《河南省城市排水防涝应急预案》、《驻马店市防汛应急预案》等，制定本预案。 |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/lark-doc/writing-types/samples/emergency-plan.sample.城市排水防涝应急预案.md` at
line 77, There is a duplicated word in the cited policy title within the preface
paragraph of the emergency plan sample. Update the reference in the long “依据…”
list so the title currently written as “河南省防汛应急应急预案” is corrected to
“河南省防汛应急预案”, keeping the rest of the cited document names unchanged.
| 专班成员（县水利局副局长）：负责调度城市防洪工程，组织水利和防汛专家提供技术支持。 | ||
| 专班成员（县应急管理局副局长）：负责应急救援抢险工作。 | ||
| 专班成员（县人防办副主任）：负责防空设施防汛抢险工作。 | ||
| 专班成员（县气象局副局长）：负责雨情预报，递进式发布暴雨及灾害性天气预警，按等级发布气象灾害预警信号，与联排联调相关部门共享雨情气象信息，面向社会公众发布有关灾害预警信息。 专班成员（柏城、柏亭、柏苑办事处副主任）：负责辖区内所管理湖泊、水系、排水管网、明沟暗渠、闸坝的调度，共享跨区河流水雨工情信息，并提供基础数据，及时反馈调度运行情况。 |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Split the two member entries into separate lines.
This line currently runs two roles together, which makes the ownership layout harder to read.
♻️ Proposed fix
-专班成员（县气象局副局长）：负责雨情预报，递进式发布暴雨及灾害性天气预警，按等级发布气象灾害预警信号，与联排联调相关部门共享雨情气象信息，面向社会公众发布有关灾害预警信息。 专班成员（柏城、柏亭、柏苑办事处副主任）：负责辖区内所管理湖泊、水系、排水管网、明沟暗渠、闸坝的调度，共享跨区河流水雨工情信息，并提供基础数据，及时反馈调度运行情况。
+专班成员（县气象局副局长）：负责雨情预报，递进式发布暴雨及灾害性天气预警，按等级发布气象灾害预警信号，与联排联调相关部门共享雨情气象信息，面向社会公众发布有关灾害预警信息。
+专班成员（柏城、柏亭、柏苑办事处副主任）：负责辖区内所管理湖泊、水系、排水管网、明沟暗渠、闸坝的调度，共享跨区河流水雨工情信息，并提供基础数据，及时反馈调度运行情况。📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| 专班成员（县气象局副局长）：负责雨情预报，递进式发布暴雨及灾害性天气预警，按等级发布气象灾害预警信号，与联排联调相关部门共享雨情气象信息，面向社会公众发布有关灾害预警信息。 专班成员（柏城、柏亭、柏苑办事处副主任）：负责辖区内所管理湖泊、水系、排水管网、明沟暗渠、闸坝的调度，共享跨区河流水雨工情信息，并提供基础数据，及时反馈调度运行情况。 | |
| 专班成员（县气象局副局长）：负责雨情预报，递进式发布暴雨及灾害性天气预警，按等级发布气象灾害预警信号，与联排联调相关部门共享雨情气象信息，面向社会公众发布有关灾害预警信息。 | |
| 专班成员（柏城、柏亭、柏苑办事处副主任）：负责辖区内所管理湖泊、水系、排水管网、明沟暗渠、闸坝的调度，共享跨区河流水雨工情信息，并提供基础数据，及时反馈调度运行情况。 |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/lark-doc/writing-types/samples/emergency-plan.sample.城市排水防涝应急预案.md` at
line 96, The member list entry currently merges two separate roles into one
line, which makes the ownership structure hard to read. In the emergency plan
sample, split the text in the affected member entry so the “专班成员（县气象局副局长）”
responsibility and the “专班成员（柏城、柏亭、柏苑办事处副主任）” responsibility are placed on
separate lines, preserving the same wording but improving readability and
alignment with the rest of the list.
| 最初，“鹅腿阿姨”走红，是一场精英高校学子对底层小摊贩的一次追捧和造神。 | ||
| 陈秀凤最早在北大校内卖水果，被学生们称作水果阿姨，后来改卖烤腿，称呼也随之变成了鹅腿阿姨。在此后十余年里，她只是高校周边一个普通的流动摊贩。2023年11月，原本主要在北大、人大周边出摊的陈秀凤转战清华，人大学生在网上发帖呼唤阿姨归来，戏称鹅腿阿姨被清华拐走，三所顶尖高校学生，“在线抢人”，清华北大鹅腿阿姨之争相关词条登上微博热搜。同年11月26日晚，清华东北门外排起长队，每个微信群每天只放出20个预订名额，中午开始接龙，不到半小时便告订满。 | ||
| 一位清华学生帮她发起了第一个鹅腿群，一天之内就成立了十几个群，此后发展到北大30多个群、人大约25个群、清华七八个群，陈秀凤每天光是翻看群消息收集订单就要忙到凌晨一两点。走红数日后，她一度暂停出摊，坦言自己只想安安静静做个烧烤，但人流量和压力都太大了。 | ||
| “鹅腿阿姨”的走红是多方合力共同推动下的产物。学生贡献了最初的情感和组织形式，建群、接龙、发帖呼唤都出自他们之手。媒体的争相报道，迅速把这种朴素的情感加工成温情叙事，搭建起勤劳的连云港夫妇、名校学生与摊贩的双向奔赴的报道框架。 |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Replace the stray “连云港夫妇” reference.
This paragraph is about陈秀凤/“鹅腿阿姨”; 连云港夫妇 looks copied from a different article and breaks factual consistency.
♻️ Proposed fix
-媒体的争相报道，迅速把这种朴素的情感加工成温情叙事，搭建起勤劳的连云港夫妇、名校学生与摊贩的双向奔赴的报道框架。
+媒体的争相报道，迅速把这种朴素的情感加工成温情叙事，搭建起陈秀凤、名校学生与媒体共同参与的温情叙事框架。📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| “鹅腿阿姨”的走红是多方合力共同推动下的产物。学生贡献了最初的情感和组织形式，建群、接龙、发帖呼唤都出自他们之手。媒体的争相报道，迅速把这种朴素的情感加工成温情叙事，搭建起勤劳的连云港夫妇、名校学生与摊贩的双向奔赴的报道框架。 | |
| “鹅腿阿姨”的走红是多方合力共同推动下的产物。学生贡献了最初的情感和组织形式，建群、接龙、发帖呼唤都出自他们之手。媒体的争相报道，迅速把这种朴素的情感加工成温情叙事，搭建起陈秀凤、名校学生与媒体共同参与的温情叙事框架。 |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/lark-doc/writing-types/samples/hotspot-analysis.sample.社会热点分析9篇.md` at
line 70, The paragraph contains an incorrect stray reference to “连云港夫妇” that
conflicts with the surrounding discussion of 陈秀凤/“鹅腿阿姨”. Update the text in this
hotspot-analysis sample so the media narrative only refers to the actual subject
of the article, and remove or replace the copied phrase with the correct entity
name while keeping the sentence flow intact.
Comment on lines
+81
to
+84
| > ❌ 他是一个非常无私奉献、深受大家爱戴的好人。 | ||
| > | ||
| > ✓ 他抽屉里常年放着速效救心丸,但谁家孩子上学有困难,他第一个掏钱。 | ||
|
|
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Remove the empty quoted line.
The blank blockquote line trips the markdownlint no-blanks-blockquote warning.
Suggested fix
> ❌ 他是一个非常无私奉献、深受大家爱戴的好人。
->
> ✓ 他抽屉里常年放着速效救心丸,但谁家孩子上学有困难,他第一个掏钱。📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| > ❌ 他是一个非常无私奉献、深受大家爱戴的好人。 | |
| > | |
| > ✓ 他抽屉里常年放着速效救心丸,但谁家孩子上学有困难,他第一个掏钱。 | |
| > ❌ 他是一个非常无私奉献、深受大家爱戴的好人。 | |
| > ✓ 他抽屉里常年放着速效救心丸,但谁家孩子上学有困难,他第一个掏钱。 |
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 84-84: Blank line inside blockquote
(MD028, no-blanks-blockquote)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/lark-doc/writing-types/samples/speech-draft.sample.anti-ai.md` around
lines 81 - 84, Remove the empty blockquoted line in the sample by updating the
quoted example around the speech draft content so there are no blank “>” lines
between the quoted sentences. Keep the surrounding examples intact and ensure
the markdown in speech-draft.sample.anti-ai.md no longer triggers markdownlint
no-blanks-blockquote.
Source: Linters/SAST tools
| 4. 善于运用正式、规范的表达方式，行文庄重、逻辑严谨，突出前瞻性与操作性的统一。 | ||
| 5. 语言精炼准确，观点鲜明有力。 | ||
| 6. 掌握抓关键、建金字塔、大小结合等战略思维技巧：能从复杂信息中提炼核心命题，构建MECE（相互独立、完全穷尽）的论点体系，做到“大处着眼、小处着手”。 | ||
| 7. 针对个体工商户和创业者的商业规划，可忽略上述结构，把落脚点放在短期内解决问题、短期内赚钱、提升实操性上，不可好高骛远。 |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Keep the strategic scaffold for small-business cases.
可忽略上述结构 is too strong here: it drops the environment/target/path/guardrails framework entirely, so this branch stops producing战略规划 and becomes a short-term execution brief. Please compress the structure instead of skipping it.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/lark-doc/writing-types/strategic-planning.md` at line 71, The
small-business guidance in the strategic-planning doc is too aggressive because
“可忽略上述结构” removes the existing strategic scaffold entirely. Update the wording
in the branch for 个体工商户和创业者 so it preserves the
environment/target/path/guardrails framework from the main structure, but
compresses it into a shorter, more practical format focused on short-term
problem solving and execution. Keep the same intent in the strategic-planning
section while ensuring the content still reads as a strategic plan rather than a
pure execution brief.
| - 用户不是学生，且写作的对象和场景不是职场场景； | ||
| - 用户写作的场景虽属职场范畴，但仅是进行业务工作上的梳理总结，不涉及个人认知上的转变或情感上的动态，此类写作任务路由至[工作总结.md](./work-summary.md)； | ||
| - 用户写作的场景虽属职场范畴，但不是以个人名义进行写作，而是以组织或团队名义进行写作，此类写作任务同样路由至[工作总结.md](./work-summary.md)； | ||
| - 用户需要的是党建思想政治领域的心得体会、学生读后感观后感、文学性的生活感悟感悟等，而不是针对具体专业学习、业务工作等领域的总结性学习心得，其中，党建思想政治领域的心得体会写作任务路由至[思想汇报.md](./political-theories-reflection.md)； |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Align the route label with the linked file.
思想汇报.md is the wrong visible label for a link that targets political-theories-reflection.md, and 生活感悟感悟 repeats the same word.
♻️ Proposed fix
-- 用户需要的是党建思想政治领域的心得体会、学生读后感观后感、文学性的生活感悟感悟等，而不是针对具体专业学习、业务工作等领域的总结性学习心得，其中，党建思想政治领域的心得体会写作任务路由至[思想汇报.md](./political-theories-reflection.md)；
+- 用户需要的是党建思想政治领域的心得体会、学生读后感观后感、文学性的生活感悟等，而不是针对具体专业学习、业务工作等领域的总结性学习心得，其中，党建思想政治领域的心得体会写作任务路由至[political-theories-reflection.md](./political-theories-reflection.md)；📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| - 用户需要的是党建思想政治领域的心得体会、学生读后感观后感、文学性的生活感悟感悟等，而不是针对具体专业学习、业务工作等领域的总结性学习心得，其中，党建思想政治领域的心得体会写作任务路由至[思想汇报.md](./political-theories-reflection.md)； | |
| - 用户需要的是党建思想政治领域的心得体会、学生读后感观后感、文学性的生活感悟等，而不是针对具体专业学习、业务工作等领域的总结性学习心得，其中，党建思想政治领域的心得体会写作任务路由至[political-theories-reflection.md](./political-theories-reflection.md)； |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/lark-doc/writing-types/work-reflection.md` at line 55, The route label
in the work-reflection guidance is mismatched with the target link, and the
phrase “生活感悟感悟” contains a duplicated word. Update the visible link text in the
sentence around the `思想汇报`/`political-theories-reflection` reference so it
matches the actual linked document name, and revise the “生活感悟感悟” wording to a
single, correct term while keeping the meaning unchanged.
liuxin-0319
force-pushed
the
chore/sync-lark-doc-from-v47-online-doc
branch
from
July 8, 2026 12:16
f4e2c69 to
2b46d06
Compare
github-actions
Bot
added
size/M
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Conflict resolution
Verification
Summary by CodeRabbit