菜单
Use when recording TiDB integration tests under tests/integrationtest and verifying regenerated result files stay minimal and correct.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/pingcap/tidb --skill tidb-integrationtest-recorder命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | tidb-integrationtest-recorder |
| description | Use when recording TiDB integration tests under tests/integrationtest and verifying regenerated result files stay minimal and correct. |
Use this workflow for changes under tests/integrationtest/t/** or when SQL behavior needs integration coverage.
Do not use -record for this suite.
Canonical command details live in docs/agents/testing-flow.md -> Integration tests (/tests/integrationtest).
docs/agents/testing-flow.md -> Integration tests (/tests/integrationtest) for the recording command.TestName from the path under tests/integrationtest/t/ without the .test suffix (example: planner/core/binary_plan).tests/integrationtest/r/** and keep result diffs minimal.Use when implementing a user- or reviewer-prescribed code change (including review comments with suggested fixes or options), especially when the requested edit may be risky, incomplete, ambiguous, or misaligned with TiDB correctness and compatibility constraints.
Use when deciding whether make bazel_prepare is required before build or test commands based on local file changes in TiDB.
Use when creating or editing TiDB GitHub issues so issue templates, labels, issue titles, and issue descriptions stay consistent with repository workflow. Trigger on tasks involving issue creation, bug reports, enhancement tracking issues, label selection, or searching for existing issues and PRs before filing a new one.
基于 SOC 职业分类
