docs(calendar): refine attendee guidance for bots and user-search identity - #2086
Conversation
…ntity Consolidate the user-search identity note into SKILL.md, and clarify bot handling across attendee flows: bots are virtual identities with no free/busy semantics, no meeting-room seat, and no room preference, so they must be excluded from +suggestion, +room-find, and the scheduling free/busy check. Note in create/update that bots remain valid attendees.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
📝 WalkthroughWalkthroughCalendar documentation clarifies bot identity search behavior, valid bot attendee usage, and when bot identities must be excluded from room and busy/free calculations. ChangesCalendar bot attendee handling
Estimated code review effort: 1 (Trivial) | ~3 minutes Possibly related PRs
Suggested labels: 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@c99176f10ff98cfe8695bb0e5b6eb9c1bc085967🧩 Skill updatenpx skills add larksuite/cli#docs/calendar-bot-attendee-guidance -y -g |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2086 +/- ##
=======================================
Coverage 75.16% 75.16%
=======================================
Files 912 912
Lines 96475 96475
=======================================
Hits 72517 72517
Misses 18381 18381
Partials 5577 5577 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Summary
Refine the calendar skill docs so AI agents handle bot participants correctly. Bots are virtual identities with no free/busy semantics, no meeting-room seat, and no room preference, so they must be dropped from time/room recommendation flows while remaining valid attendees when actually creating or updating an event.
Changes
+suggestion:--attendee-idsnote now tells agents not to pass a bot open_id, since bots have no free/busy semantics and pollute time-slot recommendations.+room-find:--attendee-idsnote plus a rules entry to strip bot attendees before querying — bots take no seat and carry no room preference.+create/+update: clarify that bots are still valid attendees to add, so the exclusion rule above is not over-applied to the landing step.Test Plan
git diff --name-only)Related Issues
Summary by CodeRabbit