New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

TiDB Verification Profiles

by pingcap in pingcap/tidb

Chooses how much validation a TiDB change needs: scoped checks while iterating, required checks at delivery, and expensive runs only when explicitly needed.

Apache-2.0Auto-check passedDevelopment

Install TiDB Verification Profiles

skills CLI
$ npx skills add pingcap/tidb --skill tidb-verify-profile -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install pingcap/tidb tidb-verify-profile --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/pingcap/tidb.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/tidb-verify-profile .claude/skills/tidb-verify-profile && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tidb-verify-profile
GitHub stars
41k
Token cost
~496 tokens
SKILL.md length
245 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
Apache-2.0

At a glance

Chooses how much validation a TiDB change needs: scoped checks while iterating, required checks at delivery, and expensive runs only when explicitly needed.

  • Works in 4 steps: Map changed paths and change types to… → Run the required checks for those… → If code changed, run make lint. → …
  • Deciding which checks to run while iterating on a TiDB change
  • SKILL.md covers Overview and Profiles
  • Calls make and go

What it does

This skill selects validation for repository changes in the TiDB codebase, whether code, formatting, documentation, testdata or build configuration. Read-only analysis needs no build or test checks. Policy still comes from AGENTS.md, and the skill acts as the execution guide for it.

It defines three profiles. WIP is for the coding loop: run only the smallest checks that cover the changed behavior, preferably targeted Go unit tests, and avoid slow sweeps such as make lint or RealTiKV tests. Ready is the completion gate: map the changed paths to the validation matrix in AGENTS.md, run the required checks, run make lint when code changed, report as the Agent Output Contract says, and reuse completed checks that still cover the delivered change. Heavy is only for expensive checks that the scope or your request require, and make bazel_lint_changed runs only if you ask.

When your agent uses it

  • Deciding which checks to run while iterating on a TiDB change
  • Preparing a TiDB pull request and confirming the required validation
  • Checking whether a formatting-only or docs-only change needs RealTiKV tests

Example prompts

  • “I changed the planner's join reorder code. Which checks do I run before opening a PR?”
  • “Run only the quick checks for this fix while I keep iterating.”
  • “Do I need RealTiKV tests for this formatting-only change?”

Requirements

  • A TiDB repository checkout with its AGENTS.md
  • Go and make

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Map changed paths and change types to AGENTS.md -> Task -> Validation Matrix and the applicable special cases in Quick Decision Matrix.
  2. Run the required checks for those changes. Preserve regression evidence for bug fixes, documentation review for agent instructions/skills…
  3. If code changed, run make lint.
  4. Follow AGENTS.md -> Agent Output Contract for final reporting.

What it can do on your machine

Read from SKILL.md and the folder at commit e39ff91. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • make
    • go

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

TiDB Verification Profiles loads about 496 tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 245 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~33
When it runs · the whole SKILL.md, loaded when a task matches
~496

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from pingcap/tidb at commit e39ff91, republished under its Apache-2.0 licence (© pingcap). 245 words, ~496 tokens.

Download SKILL.mdSave it as .claude/skills/tidb-verify-profile/SKILL.md (or your agent's skills folder).
name
tidb-verify-profile
description
Choose validation for TiDB changes during iteration and delivery, using the checks required for each change type.

TiDB Verification Profiles

Overview

Use this skill to select validation for repository changes, including code, formatting, documentation, testdata, and build configuration. Read-only analysis does not require build/test checks. Policy requirements still come from AGENTS.md; this skill is the execution guide.

Profiles

WIP (coding loop)

Use while iterating on a change.

  • Run only the smallest scoped checks that validate the changed behavior.
  • Prefer targeted unit tests (go test -run <TestName> -tags=intest,deadlock).
  • Avoid slow sweeps by default (make lint, package-wide runs, realtikvtest).
Ready (completion gate)

Use when delivering changes or preparing a PR, as defined in AGENTS.md -> Quick Decision Matrix. Select checks from the actual change type; status wording neither adds nor waives checks.

  1. Map changed paths and change types to AGENTS.md -> Task -> Validation Matrix and the applicable special cases in Quick Decision Matrix.
  2. Run the required checks for those changes. Preserve regression evidence for bug fixes, documentation review for agent instructions/skills, and scoped checks for testdata or build configuration. Formatting-only changes do not require RealTiKV tests.
  3. If code changed, run make lint.
  4. Follow AGENTS.md -> Agent Output Contract for final reporting.

Reuse completed checks that still cover the delivered changes. Rerun affected checks when relevant changes or new failures invalidate the results, not merely because another status update is due.

Heavy (explicitly required)

Use only when scope or user request requires expensive checks.

  • Examples: CI reproduction, broad refactor confidence, change scope requiring RealTiKV.
  • Never run make bazel_lint_changed unless the user explicitly requests it.

© pingcap, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/tidb-verify-profile of pingcap/tidb.

Open the folder on GitHubat commit e39ff91

Compare with similar skills

TiDB Verification Profiles next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

TiDB Verification Profiles compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
TiDB Verification Profiles this skillpingcap/tidb41k—~496Automated safety check: PassApache-2.0
Conductor Workflow Patternswshobson/agents40k9 repos~426Automated safety check: PassMIT
Procoder Commit Gateazrtydxb/procoder211—~3.7kAutomated safety check: PassApache-2.0
Post-Development WorkflowZeroDeng01/sublinkPro1.7k—~4.4kAutomated safety check: PassMIT
lo2cin4bt Acceptance Reviewlo2cin4/lo2cin4bt288—~1.4kAutomated safety check: PassCustom licence
AI SAFE2 Development MethodCyberStrategyInstitute/ai-safe2-framework146—~833Automated safety check: PassCustom licence

Similar skills

  • Conductor Workflow Patterns

    wshobson/agents

    Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the…

    40k GitHub starsUsed in 9 repos~426 tokens
    DevelopmentAuto-check passed

  • Procoder Commit Gate

    azrtydxb/procoder

    Applies Procoder's senior-developer discipline in a repository: run the commit gate, format through the binary and work through specs, plans and todos.

    211 GitHub stars~3.7k tokensUpdated 10 days ago
    DevelopmentAuto-check passed

  • Post-Development Workflow

    ZeroDeng01/sublinkPro

    A required checklist for after code changes: validate each changed layer, check that docs and other layers stay in sync, and test before committing or opening a PR.

    1.7k GitHub stars~4.4k tokensUpdated today
    DevelopmentAuto-check passed

  • lo2cin4bt Acceptance Review

    lo2cin4/lo2cin4bt

    Runs a pass, revise or block acceptance review on lo2cin4bt work, checking a deliverable against the request, repo contracts, tests, docs and the public GitHub boundary.

    288 GitHub stars~1.4k tokensUpdated 2 mo ago
    Testing & QAAuto-check passed

  • AI SAFE2 Development Method

    CyberStrategyInstitute/ai-safe2-framework

    Plans and runs material repository changes with the AI SAFE2 method: classify delivery shape and risk, isolate the work, collect test evidence and finish with a completion receipt.

    146 GitHub stars~833 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • RuView Result Verification

    ruvnet/RuView

    Proves a RuView result is real by running a deterministic SHA-256 proof and a witness bundle, and by checking reports for untagged or unreproducible accuracy claims.

    97k GitHub stars~395 tokensUpdated today
    Testing & QAAuto-check passed

More from pingcap/tidb

All 9 skills in this repo

  • TiDB Bazel Prepare Gate

    pingcap/tidb

    Decides from local git changes whether make bazel_prepare must run in TiDB before build or test commands, and reports the evidence for the decision.

    41k GitHub stars~408 tokensUpdated today
    Auto-check passed

  • TiDB Test Diff Triage

    pingcap/tidb

    Investigates TiDB plan or test-result diffs that the change does not explain, ruling out failpoint setup and merge effects before expected outputs are updated.

    41k GitHub stars~498 tokensUpdated today
    Auto-check passed

  • TiDB Failpoint Test Runner

    pingcap/tidb

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

    41k GitHub stars~256 tokensUpdated today
    Auto-check passed

  • TiDB Integration Test Recorder

    pingcap/tidb

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

    41k GitHub stars~260 tokensUpdated today
    Auto-check passed

  • TiDB RealTiKV Test Runner

    pingcap/tidb

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

    41k GitHub stars~250 tokensUpdated today
    Auto-check passed

  • TiDB Change Instruction Critic

    pingcap/tidb

    Checks a fix proposed by a user or reviewer for intent, correctness and compatibility before the agent implements it in the TiDB codebase.

    41k GitHub stars~523 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about TiDB Verification Profiles

What does TiDB Verification Profiles do?

Chooses how much validation a TiDB change needs: scoped checks while iterating, required checks at delivery, and expensive runs only when explicitly needed. This skill selects validation for repository changes in the TiDB codebase, whether code, formatting, documentation, testdata or build configuration. Read-only analysis needs no build or test checks.

When should I use TiDB Verification Profiles?

TiDB Verification Profiles fits situations like: deciding which checks to run while iterating on a TiDB change; preparing a TiDB pull request and confirming the required validation; checking whether a formatting-only or docs-only change needs RealTiKV tests.

How do I install TiDB Verification Profiles in Claude Code?

Run `npx skills add pingcap/tidb --skill tidb-verify-profile -a claude-code`. Or copy the skill folder (.agents/skills/tidb-verify-profile in pingcap/tidb) into .claude/skills/tidb-verify-profile in your project. Claude Code loads it when a task matches its description.

How do I install TiDB Verification Profiles in Codex?

Run `npx skills add pingcap/tidb --skill tidb-verify-profile -a codex`. Or copy the skill folder (.agents/skills/tidb-verify-profile in pingcap/tidb) into .agents/skills/tidb-verify-profile in your project. Codex loads it when a task matches its description.

Can I use TiDB Verification Profiles in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pingcap/tidb --skill tidb-verify-profile -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tidb-verify-profile, .gemini/skills/tidb-verify-profile, .github/skills/tidb-verify-profile and .opencode/skills/tidb-verify-profile in your project.

What does TiDB Verification Profiles need to run?

Going by SKILL.md and its folder, TiDB Verification Profiles needs the command-line tools its instructions call (make and go). Our summary lists: A TiDB repository checkout with its AGENTS.md; Go and make.

Does TiDB Verification Profiles access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is TiDB Verification Profiles safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does TiDB Verification Profiles use?

TiDB Verification Profiles is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does TiDB Verification Profiles use?

About 496 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to TiDB Verification Profiles?

Skills that share tags, products or a category with TiDB Verification Profiles: Conductor Workflow Patterns (wshobson/agents, 40k stars), Procoder Commit Gate (azrtydxb/procoder, 211 stars), Post-Development Workflow (ZeroDeng01/sublinkPro, 1.7k stars) and lo2cin4bt Acceptance Review (lo2cin4/lo2cin4bt, 288 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains TiDB Verification Profiles?

pingcap (a GitHub organization) maintains it in pingcap/tidb, which has 40,632 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 8, 2026.

Source: pingcap/tidb on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.