Skip to content

ai: add release notes SKILL#22712

Merged
ti-chi-bot[bot] merged 5 commits intopingcap:masterfrom
Oreoxmt:skill/release-notes
Apr 10, 2026
Merged

ai: add release notes SKILL#22712
ti-chi-bot[bot] merged 5 commits intopingcap:masterfrom
Oreoxmt:skill/release-notes

Conversation

@Oreoxmt
Copy link
Copy Markdown
Collaborator

@Oreoxmt Oreoxmt commented Apr 8, 2026

First-time contributors' checklist

What is changed, added or deleted? (Required)

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

  • master (the latest development version)
  • v9.0 (TiDB 9.0 versions)
  • v8.5 (TiDB 8.5 versions)
  • v8.1 (TiDB 8.1 versions)
  • v7.5 (TiDB 7.5 versions)
  • v7.1 (TiDB 7.1 versions)
  • v6.5 (TiDB 6.5 versions)
  • v6.1 (TiDB 6.1 versions)
  • v5.4 (TiDB 5.4 versions)

What is the related PR or file link(s)?

  • This PR is translated from:
  • Other reference link(s):

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

@Oreoxmt Oreoxmt added the translation/no-need No need to translate this PR. label Apr 8, 2026
@ti-chi-bot ti-chi-bot bot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Apr 8, 2026
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a comprehensive AI skill for writing, reviewing, and translating TiDB release notes, including detailed reference guides for bug fixes, improvements, and compatibility changes. The documentation establishes strict style rules for both English and Chinese content, such as specific opening verbs, inline code conventions, and bilingual alignment workflows. The review feedback focuses on improving the clarity and directness of these instructions by adhering to the style guide's preference for active voice and second-person address.

* `修复 [X] 的问题` (most common)
* `修复 [X] 可能 [崩溃/panic/卡住/报错] 的问题` (non-deterministic failures)
* `修复 [X] 导致 [Y] 的问题` (cause-effect issues)
* `禁止 [X]` (used when the fix introduces a restriction rather than a repair; rare)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

Use active voice in the parenthetical instruction to follow the style guide.

Suggested change
* `禁止 [X]` (used when the fix introduces a restriction rather than a repair; rare)
* 禁止 [X] (Use this when the fix introduces a restriction rather than a repair; rare)
References
  1. Avoid passive voice overuse. (link)

- Entry [#NNNNN](https://github.com/pingcap/tidb/issues/NNNNN) @[contributor](https://github.com/contributor)
```

Component groups use `+`, and individual entries use `-`. Tools are nested one level deeper under `+ Tools`.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

Use active voice for the instruction regarding nesting tools.

Suggested change
Component groups use `+`, and individual entries use `-`. Tools are nested one level deeper under `+ Tools`.
Component groups use `+`, and individual entries use `-`. Nest tools one level deeper under `+ Tools`.
References
  1. Avoid passive voice overuse. (link)


State the user benefit explicitly. Explain why the change matters in terms of performance, stability, or capability. For example, instead of "Not use the stale read request's `start_ts` to update `max_ts`," write "Avoid excessive commit request retrying by not using the Stale Read request's `start_ts` to update `max_ts`."

Metric claims are encouraged when sourced, such as "up to 10 times performance improvement" or "improves performance by up to 62.5%."
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

Use active voice and address the user directly to encourage best practices.

Suggested change
Metric claims are encouraged when sourced, such as "up to 10 times performance improvement" or "improves performance by up to 62.5%."
Encourage metric claims when you have a source, such as "up to 10 times performance improvement" or "improves performance by up to 62.5%."
References
  1. Write in second person ('you') when addressing users. (link)
  2. Avoid passive voice overuse. (link)

Copy link
Copy Markdown
Collaborator

@qiancai qiancai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rest LGTM

@ti-chi-bot
Copy link
Copy Markdown

ti-chi-bot bot commented Apr 10, 2026

[LGTM Timeline notifier]

Timeline:

  • 2026-04-10 01:17:08.589234878 +0000 UTC m=+1091833.794594925: ☑️ agreed by qiancai.

@ti-chi-bot ti-chi-bot bot added the needs-1-more-lgtm Indicates a PR needs 1 more LGTM. label Apr 10, 2026
Oreoxmt and others added 2 commits April 10, 2026 10:35
Co-authored-by: Grace Cai <qqzczy@126.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
@Oreoxmt
Copy link
Copy Markdown
Collaborator Author

Oreoxmt commented Apr 10, 2026

/retest

@Oreoxmt Oreoxmt added the lgtm label Apr 10, 2026
@Oreoxmt
Copy link
Copy Markdown
Collaborator Author

Oreoxmt commented Apr 10, 2026

/approve

@ti-chi-bot
Copy link
Copy Markdown

ti-chi-bot bot commented Apr 10, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Oreoxmt

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot bot added the approved label Apr 10, 2026
@ti-chi-bot ti-chi-bot bot merged commit ea7e897 into pingcap:master Apr 10, 2026
11 of 14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved lgtm needs-1-more-lgtm Indicates a PR needs 1 more LGTM. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. translation/no-need No need to translate this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants