ai: add docs-pr-metadata-guard and docs-issue-metadata-guard skills#23051
Conversation
ti-chi-bot
Bot
added
missing-translation-status
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces two new AI skills, docs-pr-metadata-guard and docs-issue-metadata-guard, and updates .ai/AI-README.md and AGENTS.md to document them. These skills guide the preservation of template structures, required fields, and metadata conventions for pull requests and issues. The review feedback points out several headings in the new skill files that violate the repository style guide requiring sentence case.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
ti-chi-bot
Bot
removed
the
missing-translation-status
[LGTM Timeline notifier]Timeline:
|
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: qiancai The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
2 participants
What is changed, added or deleted? (Required)
Add two new AI agent skills under
.ai/skills/and register them inAGENTS.mdand.ai/AI-README.md:docs-pr-metadata-guard: guides AI agents to preserve the PR template structure when creating or editing pull requests — including version checkboxes, required description sections, HTML comments, related-link fields, base branch selection, cherry-pick label conventions, and the first-time contributors' checklist.docs-issue-metadata-guard: guides AI agents to use the correct issue template (Error Report, Change Request, or Question) when creating or editing issues — including required fields, docs-only scope enforcement, template structure preservation, and label hygiene.Why these skills are needed:
When human contributors create PRs or issues through the GitHub web UI, the repository templates are pre-loaded automatically, so the required structure is naturally followed. However, when AI agents create PRs or issues via the
ghCLI, these templates are not enforced — the agent can easily skip the template entirely, produce a freeform body, omit version checkboxes, or ignore required fields. These two skills close that gap by giving agents explicit instructions to read and follow the repository templates before callinggh, ensuring agent-created PRs and issues meet the same structural standards as human-created ones.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.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?