From 0bc1d0a508fc28d6a36b0c0e169ef83f76432ddc Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Mon, 6 Oct 2025 14:13:52 +0000
Subject: [PATCH 1/2] Initial plan


From 859c0b3fb4dafd365a209117a893cf4099b07d6a Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Mon, 6 Oct 2025 14:20:58 +0000
Subject: [PATCH 2/2] docs: create improve-doc-authenticity.prompt.yml for code
 example quality

Co-authored-by: chenjiahan <7237365+chenjiahan@users.noreply.github.com>
---
 .github/improve-doc-authenticity.prompt.yml | 43 +++++++++++++++++++++
 1 file changed, 43 insertions(+)
 create mode 100644 .github/improve-doc-authenticity.prompt.yml

diff --git a/.github/improve-doc-authenticity.prompt.yml b/.github/improve-doc-authenticity.prompt.yml
new file mode 100644
index 0000000000..e5e214fdce
--- /dev/null
+++ b/.github/improve-doc-authenticity.prompt.yml
@@ -0,0 +1,43 @@
+messages:
+  - role: system
+    content: >-
+      Improve the authenticity and accuracy of documentation in `website/docs`.
+      Focus on making code examples, configurations, and technical details more
+      accurate and representative of real-world usage.
+
+
+      Enhance documentation to ensure code examples are **accurate, runnable,
+      and realistic** — matching the quality standards of professional
+      open-source documentation.
+
+
+      - **IMPORTANT:** Verify that code examples actually work and follow best
+      practices.
+
+      - **IMPORTANT:** Ensure configuration examples are complete and valid.
+
+      - **IMPORTANT:** Don't change working examples unless there's a clear
+      accuracy or best practice improvement.
+
+      - If you update code examples, test them when possible to ensure they
+      work correctly.
+
+      - Update both English (`docs/en`) and Chinese (`docs/zh`) versions when
+      making changes to code examples or technical content.
+
+      - Use realistic variable names and values (not placeholder text like
+      'foo', 'bar' unless demonstrating a concept).
+
+      - Ensure import statements and dependencies match what's actually
+      available in the package.
+
+      - Add missing error handling or edge cases in examples when appropriate.
+
+      - Verify that file paths, package names, and API references are correct.
+
+      - Keep examples simple but complete enough to be useful.
+
+      - Don't change more than 10 files in one PR.
+
+      - Start PR titles with `docs:`.
+model: openai/gpt-5