Menu
Publish a new release of the Feishu plugin. Use when the user asks to release, publish, or cut a new version.
Feishu message emoji reactions. Activate when user mentions emoji, reaction, thumbsup, like, or responding to messages with emoji.
Feishu message reading. Activate when user mentions reading messages, chat history, message lookup, or finding previous messages.
Feishu urgent message (buzz) notifications. Activate when user mentions urgent, buzz, remind, or escalation for messages.
Feishu document read/write operations + comment management. Activate when user mentions Feishu docs, cloud docs, docx links, or document comments.
Feishu Task, tasklist, subtask, comment, and attachment management. Activate when user mentions tasks, tasklists, subtasks, task comments, task attachments, or task links.
Local E2E debug and test framework for clawd-feishu plugin development. Use when debugging message flow, testing bot responses, verifying Feishu web UI interactions, or performing end-to-end validation of the OpenClaw-Feishu integration during development.
| name | release |
| description | Publish a new release of the Feishu plugin. Use when the user asks to release, publish, or cut a new version. |
| allowed-tools | Bash(npm version:*), Bash(npm publish:*), Bash(npx tsc:*), Bash(gh release:*), Bash(git tag:*), Bash(git push:*) |
Publish a new version of @m1heng-clawd/feishu to npm and create a GitHub release.
main)npm login session is active with publish access to @m1heng-clawd scopegh CLI is authenticatedCheck what changed since the last release:
# Find latest release tag
gh release list --limit 1
# Review commits and diff stat
git log <last-tag>..HEAD --oneline
git diff <last-tag>..HEAD --stat
Choose bump type: patch (bug fixes), minor (new features), or major (breaking changes).
npx tsc --noEmit
Do NOT proceed if type check fails.
Review the full diff to write release notes:
git diff <last-tag>..HEAD
Create a GitHub release draft first:
gh release create v<new-version> --draft --title "v<new-version>" --target main --notes "<release notes markdown>"
Edit package.json to update the "version" field to <new-version>.
git add package.json
git commit -m "chore: bump version to <new-version>"
git tag v<new-version>
git push && git push --tags
npm publish
If auth fails, ask the user to run npm login first, then retry.
gh release edit v<new-version> --draft=false
Follow the established format (see previous releases for reference):
## Features
- **Feature title** — Description. (#PR)
## Bug Fixes
- **Fix title** — Description. (#PR)
## Internal
- Internal change description.
npm login # re-authenticate
npm whoami # verify logged in
npm publish # retry
If the tag was created but publish failed, delete and recreate after fixing:
git tag -d v<version>
git push origin :refs/tags/v<version>
# fix issue, then re-tag and push