tidb-test-guidelines
Defines best practices for writing and locating tests within the TiDB codebase.
Install
mkdir -p .claude/skills/tidb-test-guidelines && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2598" && unzip -o skill.zip -d .claude/skills/tidb-test-guidelines && rm skill.zipInstalls to .claude/skills/tidb-test-guidelines
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Decide where to place TiDB tests and how to write them (basic structure, naming, testdata usage). Use when asked about test locations, writing conventions, shard_count limits, casetest categorization, or when reviewing test changes in code review.Key capabilities
- →Organize test files by package
- →Apply TiDB naming conventions
- →Manage testdata fixtures
- →Align tests with shard_count limits
How it works
It enforces standardized rules for test placement, naming, and data usage, ensuring consistency across the TiDB codebase through specific directory and file patterns.
Inputs & outputs
When to use tidb-test-guidelines
- →Determine where to place new tests
- →Apply TiDB testing naming conventions
- →Review test code quality
About tidb-test-guidelines
Provides rules for test organization, naming conventions, and data usage to ensure testing consistency across the TiDB project.
Decide where to place TiDB tests and how to write them (basic structure, naming, testdata usage). Use when asked about test locations, writing conventions, shard_count limits, casetest categorization, or when reviewing test changes in code review.
When not to use it
- →When writing tests for non-TiDB projects
- →When ignoring existing testdata patterns
Limitations
- →Requires updating case maps for certain packages
- →Strict adherence to shard_count targets is required
How it compares
It provides project-specific guidelines for test organization and assertion styles rather than relying on generic Go testing practices.
Compared to similar skills
tidb-test-guidelines side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| tidb-test-guidelines (this skill) | 2 | 27d | No flags | Intermediate |
| go-dev-guidelines | 14 | 9mo | No flags | Intermediate |
| code-formatting | 1 | 2mo | No flags | Beginner |
| lsp-hover-testing | 1 | 8mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
go-dev-guidelines
jumppad-labs
This skill should be used when writing, refactoring, or testing Go code. It provides idiomatic Go development patterns, TDD-based workflows, project structure conventions, and testing best practices using testify/require and mockery. Activate this skill when creating new Go features, services, packages, tests, or when setting up new Go projects.
code-formatting
openshift
MANDATORY: When writing Go tests, you MUST use 'When...it should...' format for ALL test names. When writing any Go code, you MUST remind user to run 'make lint-fix' and 'make verify'. These are non-negotiable HyperShift requirements.
lsp-hover-testing
MadAppGang
Automated LSP hover validation for Dingo transpiler. Use when testing hover functionality, validating position mappings, checking for hover drift, or debugging LSP issues after sourcemap changes.
go-rig
mudrii
Use this skill when building, reviewing, or refactoring Go code in this repository. It adds process discipline for TDD/ATDD, package boundaries, dependency injection, and review quality, and complements the always-on rules in AGENTS.md.
code-coverage
viknesh20-20
Analyzes test coverage, identifies untested code paths, and generates tests for the most critical uncovered areas. Use to improve test coverage before releases.
go-review-pr
JotJunior
Review all changes in the current branch against GOB project conventions before opening a PR. Diff-aware: only analyzes what changed, not the entire codebase. Triggers: \"review pr\", \"revisar pr\", \"pre-pr check\", \"review branch\", \"revisar branch\", \"checar antes do pr\", \"quality gate\".