What problem does it solve?
Developers working on TiDB often waste time running slow, broad validation commands during active coding, or under-validate before claiming completion. This Skill defines clear verification profiles so you run the right checks at the right stage of work.
Core Features & Use Cases
- WIP Profile: Run only minimal, targeted checks (e.g.,
go test -run <TestName> -tags=intest,deadlock) while iterating, avoiding slow sweeps like make lint or realtikvtest.
- Ready Profile: Before claiming completion, map changed paths to required test surfaces via the AGENTS.md validation matrix, run required targeted tests, and run
make lint if code changed.
- Heavy Profile: Reserve expensive checks (CI reproduction, RealTiKV) for explicitly required scenarios; never run
make bazel_lint_changed unless the user requests it.
- Use Case: While fixing a planner bug, you run only the targeted unit test during iteration, then switch to the Ready profile to run the mapped test surfaces and lint before reporting completion.
Quick Start
Ask the assistant to apply the TiDB verification profiles to decide which tests and lint checks to run for your current code changes.
