Skip to content

docs(skills): clarify minutes routing semantics#591

Open
zhicong666-bytedance wants to merge 1 commit intomainfrom
docs/minutes-skill-routing
Open

docs(skills): clarify minutes routing semantics#591
zhicong666-bytedance wants to merge 1 commit intomainfrom
docs/minutes-skill-routing

Conversation

@zhicong666-bytedance
Copy link
Copy Markdown
Collaborator

@zhicong666-bytedance zhicong666-bytedance commented Apr 21, 2026

Summary

Clarify the routing between VC meeting notes and minutes metadata in the skill docs.
Also refine the natural-language guidance for "participated minutes" so agents do not under-fetch owner-owned minutes.

Changes

  • clarify that minute metadata requests should route through vc +recording and minutes minutes get, rather than vc +notes
  • update the minutes search guidance so "participated minutes" defaults to the union of owner and participant results
  • fix the incorrect minute_token source in the minutes download reference
  • update the VC search/recording references to point to the correct follow-up commands for minutes metadata vs notes content

Test Plan

  • Reviewed the updated skill and reference docs in the branch diff
  • Ran git diff --check
  • Verified the documented command routing with local CLI help / dry-run checks
  • Ran go test ./...

Related Issues

  • None

Summary by CodeRabbit

  • Documentation
    • Clarified workflows for retrieving meeting minutes metadata and content.
    • Updated command guidance to distinguish between meeting notes and minute information retrieval.
    • Reorganized routing rules to properly separate search, basic info, and transcript/summary queries.
    • Improved documentation on obtaining minute metadata before fetching full content.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 21, 2026

📝 Walkthrough

Walkthrough

This PR updates documentation across the lark-minutes and lark-vc skills to clarify routing and workflows for retrieving meeting minutes and notes. It shifts minute_token retrieval to use vc +recording instead of vc +notes, establishes clear skill boundaries, and refines guidance for interpreting "participating minutes" searches.

Changes

Cohort / File(s) Summary
Lark-minutes Core Skill
skills/lark-minutes/SKILL.md
Restructured search routing rules and view-minutes-info flow control to obtain minute_token via VC link before calling minutes minutes get; delegated "my/participating minutes" interpretation to minutes +search with updated numbering.
Lark-minutes References
skills/lark-minutes/references/lark-minutes-download.md, skills/lark-minutes/references/lark-minutes-search.md
Updated minute_token acquisition from vc +notes --meeting-ids to vc +recording --meeting-ids; expanded search guidance to distinguish strict participant filtering from natural-language union queries (owner + participant); clarified downstream routing to vc +recordingminutes minutes get for minute metadata.
Lark-vc Skill & References
skills/lark-vc/SKILL.md, skills/lark-vc/references/lark-vc-recording.md, skills/lark-vc/references/lark-vc-search.md
Added boundary directive clarifying +notes scope; updated Agent scenarios to include minute basic-info retrieval via vc +recordingminutes minutes get; expanded troubleshooting to prevent unintended vc +notes routing; added reference links and refined downstream guidance.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~22 minutes

Possibly related PRs

Suggested labels

domain/vc, size/M

Suggested reviewers

  • zhaoleibd
  • liangshuo-1

Poem

🐰 Whiskers twitch with glee so keen,
Routes now clear, no more unseen!
Recording → token → minutes flow,
Boundaries drawn, the pathways glow, 🌟
Clarity hops where confusion would creep!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely summarizes the main change: clarifying minutes routing semantics in skill documentation.
Description check ✅ Passed The PR description includes all required sections from the template with substantive content: Summary explains the motivation, Changes lists concrete modifications, Test Plan documents verification steps, and Related Issues is addressed.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/minutes-skill-routing

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions github-actions Bot added domain/vc PR touches the vc domain size/L Large or sensitive change across domains or core paths labels Apr 21, 2026
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
skills/lark-vc/references/lark-vc-recording.md (1)

108-121: ⚠️ Potential issue | 🟡 Minor

Use explicit date in Scenario 4 to match current date-handling guidance.

This section’s example still uses --start yesterday, which conflicts with nearby docs that require concrete dates for deterministic routing.

Proposed doc patch
-# 第 1 步:搜索历史会议,拿到 meeting_ids
-lark-cli vc +search --query "周会" --start yesterday
+# 第 1 步:搜索历史会议,拿到 meeting_ids(示例使用明确日期)
+lark-cli vc +search --query "周会" --start 2026-03-10 --end 2026-03-10
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@skills/lark-vc/references/lark-vc-recording.md` around lines 108 - 121,
Scenario 4 uses a relative date flag "--start yesterday" in the lark-cli vc
+search example which conflicts with the deterministic routing requirement;
update the example invocation (the lark-cli vc +search command) to use an
explicit concrete date (e.g., ISO date like 2026-04-20 or a clear placeholder
such as <YYYY-MM-DD>) instead of "yesterday" so that the search step returns
deterministic meeting_ids and the subsequent lark-cli vc +recording and lark-cli
minutes +download steps remain reproducible.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@skills/lark-vc/references/lark-vc-recording.md`:
- Around line 108-121: Scenario 4 uses a relative date flag "--start yesterday"
in the lark-cli vc +search example which conflicts with the deterministic
routing requirement; update the example invocation (the lark-cli vc +search
command) to use an explicit concrete date (e.g., ISO date like 2026-04-20 or a
clear placeholder such as <YYYY-MM-DD>) instead of "yesterday" so that the
search step returns deterministic meeting_ids and the subsequent lark-cli vc
+recording and lark-cli minutes +download steps remain reproducible.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: cf78564b-970e-4696-95a7-b54e46ff5fe6

📥 Commits

Reviewing files that changed from the base of the PR and between 04e3a28 and 2db1405.

📒 Files selected for processing (6)
  • skills/lark-minutes/SKILL.md
  • skills/lark-minutes/references/lark-minutes-download.md
  • skills/lark-minutes/references/lark-minutes-search.md
  • skills/lark-vc/SKILL.md
  • skills/lark-vc/references/lark-vc-recording.md
  • skills/lark-vc/references/lark-vc-search.md

@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 21, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 61.05%. Comparing base (fbed6be) to head (2db1405).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #591      +/-   ##
==========================================
+ Coverage   60.92%   61.05%   +0.12%     
==========================================
  Files         399      400       +1     
  Lines       34089    34130      +41     
==========================================
+ Hits        20770    20838      +68     
+ Misses      11395    11368      -27     
  Partials     1924     1924              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@github-actions
Copy link
Copy Markdown

🚀 PR Preview Install Guide

🧰 CLI update

npm i -g https://pkg.pr.new/larksuite/cli/@larksuite/cli@2db1405e5ba4eebac1a998644f75b5f3b28b5e2e

🧩 Skill update

npx skills add larksuite/cli#docs/minutes-skill-routing -y -g

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

domain/vc PR touches the vc domain size/L Large or sensitive change across domains or core paths

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant