docs: add im chat member delete notes#229
Conversation
github-actions
bot
added
domain/im
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughAdded documentation for the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
|
Greptile SummaryThis is a docs-only PR that adds a Confidence Score: 5/5Safe to merge — purely additive documentation with no runtime impact. All changes are documentation-only. The new entry is correctly placed, uses consistent formatting, and the assigned scope No files require special attention. Important Files Changed
Sequence DiagramsequenceDiagram
participant Caller as Caller (user/bot)
participant LarkCLI as lark-cli
participant LarkAPI as Lark IM API
Caller->>LarkCLI: lark-cli im chat.members delete --chat-id oc_xxx --member-ids [...]
LarkCLI->>LarkAPI: DELETE /im/v1/chats/{chat_id}/members<br/>scope: im:chat.members:write_only
Note over LarkAPI: Validates caller is owner / admin / creator bot<br/>Enforces limit: ≤50 users or ≤5 bots
alt Success
LarkAPI-->>LarkCLI: 200 OK
LarkCLI-->>Caller: Members removed
else Caller lacks permission
LarkAPI-->>LarkCLI: 403 Forbidden
LarkCLI-->>Caller: Error: not owner/admin/creator-bot
else Batch limit exceeded
LarkAPI-->>LarkCLI: 400 Bad Request
LarkCLI-->>Caller: Error: too many members in one request
end
Reviews (2): Last reviewed commit: "docs: add im chat member delete scope no..." | Re-trigger Greptile |
![coderabbitai[bot]](https://waps.l3s.uni-hannover.de/live/im_/https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (1)
skills/lark-im/SKILL.md (1)
90-90: Consider expanding the documentation to match the detail level ofchat.members.create.The documentation for
chat.members.deleteis more concise thanchat.members.create(line 89). Consider adding details about:
- Whether the caller must be in the target chat
- Tenant restrictions for internal chats (operator must belong to same tenant)
- App availability constraints for bot calls
- Whether members can remove themselves (the phrase "remove others" implies this but isn't explicit)
This would ensure consistent documentation detail across related operations.
📝 Example expanded documentation
- - `delete` — 将用户或机器人移出群聊。Identity: supports `user` and `bot`; only group owner, admin, or creator bot can remove others; max 50 users or 5 bots per request. + - `delete` — 将用户或机器人移出群聊。Identity: supports `user` and `bot`; the caller must be in the target chat; only group owner, admin, or creator bot can remove others (members can remove themselves); for internal chats the operator must belong to the same tenant; for `bot` calls, removed users must be within the app's availability; max 50 users or 5 bots per request.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/lark-im/SKILL.md` at line 90, Update the `chat.members.delete` documentation to match the detail level of `chat.members.create`: explicitly state whether the caller must be present in the target chat, clarify tenant restrictions for internal chats (operator must belong to the same tenant), document app availability constraints when the caller is a bot (which bots can call this API and under what permissions), and state whether members are allowed to remove themselves versus only removing others; reference the `chat.members.delete` and `chat.members.create` entries so the wording and parameter/permission details mirror the existing `create` doc style for consistency.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@skills/lark-im/SKILL.md`:
- Line 90: Update the `chat.members.delete` documentation to match the detail
level of `chat.members.create`: explicitly state whether the caller must be
present in the target chat, clarify tenant restrictions for internal chats
(operator must belong to the same tenant), document app availability constraints
when the caller is a bot (which bots can call this API and under what
permissions), and state whether members are allowed to remove themselves versus
only removing others; reference the `chat.members.delete` and
`chat.members.create` entries so the wording and parameter/permission details
mirror the existing `create` doc style for consistency.
🚀 PR Preview Install Guide🧰 CLI updatenpm i -g https://pkg.pr.new/larksuite/cli/@larksuite/cli@d8942cd9f183ce9f848f355b7a92d7cc99a049d0🧩 Skill updatenpx skills add niuchong0523/cli#feature/add-delete-chat-members-command -y -g |
Document the IM chat member delete API and required scope so the new capability is visible in the IM skill reference.
niuchong0523
force-pushed
the
feature/add-delete-chat-members-command
branch
from
057b007 to
d8942cd
Compare
3 participants
Summary
chat.members.deleteTest plan
skills/lark-im/SKILL.mdis included🤖 Generated with Claude Code
Summary by CodeRabbit