diff --git a/.github/workflows/auto-comment-issue.yml b/.github/workflows/auto-comment-issue.yml
new file mode 100644
index 0000000000..3241ccde68
--- /dev/null
+++ b/.github/workflows/auto-comment-issue.yml
@@ -0,0 +1,51 @@
+name: auto comment on issue
+on:
+  issues:
+    types: [opened]
+jobs:
+  auto-comment:
+    runs-on: ubuntu-latest
+    steps:
+      - name: new feature
+        if: ${{ contains(github.event.issue.title, 'Feature') }} || ${{ contains(github.event.issue.title, 'Feat') }} || ${{ contains(github.event.issue.title, '新特性') }}
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'create-comment'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          issue-number: ${{ github.event.issue.number }}
+          body: |
+            Thank you for your feedback! We have received your question and will deal with it later.
+            If any developer is interested in this issue, please leave a message "claim this issue" below the issue. Welcome to participate in open source co-construction!
+            We are very grateful to every contributor. After submitting the PR, we will prepare a gift for the developers who participated in the co-construction.
+            For participation in co-construction, please refer to: https://visactor.io/vchart/contributing/
+            To communicate with official developers, you can download the Feishu app and scan the QR code to join the Feishu group！
+            Thank you again for your support!
+            ![feishu-qr-code](https://lf9-dp-fe-cms-tos.byteorg.com/obj/bit-cloud/feishu-qrcode.png)
+            感谢您的反馈！我们已经收到您的问题，并会在稍后处理。
+            如果有开发者对这个问题感兴趣，请在问题下方留言“认领此问题”。欢迎参与开源共建！
+            我们非常感谢每一位贡献者。提交 PR 后，我们会为参与共建的开发者准备一份礼物。
+            参与共建请参考：https://visactor.io/vchart/contributing/
+            如需与官方开发者沟通，可以下载飞书应用并扫描二维码加入飞书群！
+            再次感谢您的支持！
+
+      - name: doc
+        if: ${{ contains(github.event.issue.title, 'Documentation') }} || ${{ contains(github.event.issue.title, 'Doc') }} || ${{ contains(github.event.issue.title, '文档') }}
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'create-comment'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          issue-number: ${{ github.event.issue.number }}
+          body: |
+            Thank you for your feedback! We have received your question and will deal with it later.
+            If any developer is interested in this issue, please leave a message "claim this issue" below the issue. Welcome to participate in open source co-construction!
+            We are very grateful to every contributor. After submitting the PR, we will prepare a gift for the developers who participated in the co-construction.
+            For participation in co-construction, please refer to: https://visactor.io/vchart/contributing/
+            To communicate with official developers, you can download the Feishu app and scan the QR code to join the Feishu group！
+            Thank you again for your support!
+            ![feishu-qr-code](https://lf9-dp-fe-cms-tos.byteorg.com/obj/bit-cloud/feishu-qrcode.png)
+            感谢您的反馈！我们已经收到您的问题，并会在稍后处理。
+            如果有开发者对这个问题感兴趣，请在问题下方留言“认领此问题”。欢迎参与开源共建！
+            我们非常感谢每一位贡献者。提交 PR 后，我们会为参与共建的开发者准备一份礼物。
+            参与共建请参考：https://visactor.io/vchart/contributing/
+            如需与官方开发者沟通，可以下载飞书应用并扫描二维码加入飞书群！
+            再次感谢您的支持！
diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml
index a029fc90a1..1ee2e48a33 100644
--- a/.github/workflows/stale.yml
+++ b/.github/workflows/stale.yml
@@ -20,7 +20,7 @@ jobs:
       - uses: actions/stale@v5
         with:
           repo-token: ${{ secrets.GITHUB_TOKEN }}
-          days-before-stale: 730
+          days-before-stale: 90
           days-before-close: 7
           stale-issue-message: 'This issue has been automatically marked as stale because it did not have recent activity. It will be closed in 7 days if no further activity occurs. If you wish not to mark it as stale, please leave a comment in this issue.'
           close-issue-message: 'This issue has been automatically closed because it did not have recent activity. If this remains to be a problem with the latest version of @VisActor/VChart, please open a new issue and link this to it. Thanks!'