tidb

Use when deciding whether make bazel_prepare is required before build or test commands based on local file changes in TiDB.

Assess user- or reviewer-proposed TiDB fixes before implementation for intent, correctness, and compatibility.

Use when running TiDB package tests and deciding whether failpoint enable/disable is required before and after the test command.

Use when recording TiDB integration tests under tests/integrationtest and verifying regenerated result files stay minimal and correct.

Create or edit TiDB issues, choose labels, or check for duplicates before filing.

Create or edit TiDB PR metadata, or diagnose template-related bot labels; preserve required fields and hidden comments.

Use when running tests under tests/realtikvtest that require a local TiUP playground lifecycle with strict startup, readiness checks, and cleanup.

Investigate unexpected TiDB plan or test-result diffs unexplained by the change, including merge and environment effects.

Choose validation for TiDB changes during iteration and delivery, using the checks required for each change type.