feat: support semantic recurring calendar operations

[calendar-assistant]

Summary

This PR adds semantic guidance for operating on recurring calendar events so agents can choose the correct workflow for single-instance, full-series, and this-and-following edits or deletions.

Changes

• Add skills/lark-calendar/references/lark-calendar-recurring.md with operation flows for recurring event scopes: only this instance, all instances, and this-and-following.
• Clarify original recurring event IDs, expanded instance IDs, and exception events so agents use the right event_id for each operation.
• Route recurring edit/delete intents from skills/lark-calendar/SKILL.md and lark-calendar-update.md to the new recurring operation spec.
• Document exception handling requirements so full-series and this-and-following operations do not leave detached exception events behind.

Test Plan

• Verified the branch has one commit relative to origin/main: git log --oneline origin/main..HEAD.
• Reviewed the final diff against origin/main to confirm the PR only updates calendar skill documentation.
• Unit tests pass. Not run because this is a skill documentation-only change.
• Manual local verification confirms the lark-cli calendar recurring event flow works as expected. Not run because this PR updates agent operation guidance rather than CLI command behavior.

Related Issues

• None

Summary by CodeRabbit

• New Features

  • Added clear guidance for handling recurring calendar events, including “only this occurrence,” “all occurrences,” and “this and following occurrences.”
  • Introduced explicit instructions for identifying the correct event to edit and handling recurring-event exceptions safely.

• Bug Fixes

  • Improved routing so edit/delete actions for recurring events now require confirming the operation scope first.
  • Added a brief wait before rechecking changes to help avoid stale results.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: f85236f5-d5d1-4dba-9391-411eccdf45e6

📥 Commits

Reviewing files that changed from the base of the PR and between 8189636 and b3e727d.

📒 Files selected for processing (3)

• skills/lark-calendar/SKILL.md
• skills/lark-calendar/references/lark-calendar-recurring.md
• skills/lark-calendar/references/lark-calendar-update.md

✅ Files skipped from review due to trivial changes (1)

• skills/lark-calendar/references/lark-calendar-update.md

🚧 Files skipped from review as they are similar to previous changes (2)

• skills/lark-calendar/references/lark-calendar-recurring.md
• skills/lark-calendar/SKILL.md

---

📝 Walkthrough

Walkthrough

Calendar skill guidance now routes recurring edits and deletions through a scope-based reference. The new recurring operations document defines instance and series event_id rules, exception handling, and command flows for each recurring scope.

Changes

Lark calendar recurring schedule guidance

Layer / File(s)	Summary
Routing and event_id rules skills/lark-calendar/SKILL.md, skills/lark-calendar/references/lark-calendar-update.md	Recurring edit/delete intents now point to the recurring-operations reference, and update guidance requires choosing the operation scope before selecting an event_id.
Recurring spec basics skills/lark-calendar/references/lark-calendar-recurring.md	The new reference defines recurring event_id structure, exception handling, and the prerequisite checks for locating the master event, instances, and intended scope.
Recurring operation flows skills/lark-calendar/references/lark-calendar-recurring.md	The reference adds step-by-step flows for editing, deleting, truncating, and replacing recurring series, plus single-occurrence handling, intent-to-scope mapping, and UNTIL/time calculation rules.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Suggested reviewers: hugang-lark

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: semantic recurring calendar operations.
Description check	✅ Passed	The description follows the required template and includes summary, changes, test plan, and related issues.
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/calendar-recurring-operations

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.42%. Comparing base (d0cde9a) to head (b3e727d).
⚠️ Report is 18 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1723      +/-   ##
==========================================
- Coverage   74.51%   74.42%   -0.09%     
==========================================
  Files         852      854       +2     
  Lines       87655    88477     +822     
==========================================
+ Hits        65312    65852     +540     
- Misses      17315    17555     +240     
- Partials     5028     5070      +42     

☔ View full report in Codecov by Harness.
📢 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]

🚀 PR Preview Install Guide

🧰 CLI update

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

🧩 Skill update

npx skills add larksuite/cli#feat/calendar-recurring-operations -y -g

[coderabbitai]

Actionable comments posted: 2

🤖 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-calendar/references/lark-calendar-recurring.md`:
- Around line 22-25: The recurring-calendar guide incorrectly tells users to
delete all exceptions after shifting the master series, which would discard
user-specific edits. Update the instructions in lark-calendar-recurring.md to
avoid unconditional deletion: either describe how to preserve or remap
exceptions when calling lark-cli calendar +update for the master event, or
clearly mark deletion as an explicit, user-confirmed destructive step. Keep the
guidance aligned with the recurring update flow and the delete command only if
it is truly optional and intentional.
- Around line 49-53: Clarify the UNTIL rule in the recurring calendar docs by
updating the wording in the references around the split/edit flow to distinguish
timed versus all-day recurrences. In the recurring update guidance near the
`lark-cli calendar +update`, `events delete`, and `+create` steps, replace the
vague “第 N-1 次实例的日期/截止日期” phrasing with exact previous occurrence date-time for
timed events, and reserve date-only UNTIL wording for all-day events. Keep the
same terminology consistent across the related sections (including the later
rule explanation) so readers can apply the `UNTIL` calculation unambiguously.

🪄 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: 080ab282-0db9-4d71-9c7a-e77c92e6a75f

📥 Commits

Reviewing files that changed from the base of the PR and between d539841 and 8189636.

📒 Files selected for processing (3)

• skills/lark-calendar/SKILL.md
• skills/lark-calendar/references/lark-calendar-recurring.md
• skills/lark-calendar/references/lark-calendar-update.md