菜单
Run the relevant tests for what changed — detects whether to run C# unit tests, specific test projects, integration tests, or JS/TS tests based on changed files. Use when the user asks to run tests, verify changes, or check if something is broken.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Stage relevant files and create a well-formed git commit for the docs-builder repo. Use this when the user asks to commit changes, save work, or create a commit.
Auto-fix all formatting issues in the docs-builder repo — runs dotnet format for C# and npm fmt:write for TypeScript/JS. Use when the user asks to fix formatting, lint the code, or when a pre-commit hook fails due to formatting.
Create a GitHub pull request for the current branch with a focused why/what body and exactly one release-drafter label. Use when the user asks to open a PR, create a pull request, or ship a branch.
Review changed or staged C# code against the docs-builder coding standards and flag violations. Use when the user asks to review code style, check for standards violations, or audit a diff before committing.
Search, analyze, and author Elastic documentation using the remote MCP server. Use this when the user asks about Elastic product documentation, features, or APIs; wants to find, read, or verify existing docs pages; is writing or editing documentation; mentions cross-links between repos; asks about documentation structure, coherence, or consistency; wants to generate templates following Elastic content type guidelines; or references elastic.co/docs URLs or Elastic product names.
| name | test |
| description | Run the relevant tests for what changed — detects whether to run C# unit tests, specific test projects, integration tests, or JS/TS tests based on changed files. Use when the user asks to run tests, verify changes, or check if something is broken. |
Runs the right tests for what changed — fast feedback without running everything.
git diff --name-only HEAD
Or, if checking staged changes:
git diff --name-only --staged
Use this decision table based on which directories have changed files:
| Changed path | Test command |
|---|---|
src/Elastic.Documentation.Site/ | cd src/Elastic.Documentation.Site && npm run test |
src/Elastic.Markdown/ | dotnet test tests/Elastic.Markdown.Tests/ |
src/Elastic.Documentation.Configuration/ | dotnet test tests/Elastic.Documentation.Configuration.Tests/ |
src/Elastic.Documentation.Navigation/ or Navigation.Tests/ | dotnet test tests/Navigation.Tests/ |
src/Elastic.ApiExplorer/ | dotnet test tests/Elastic.ApiExplorer.Tests/ |
tests-integration/ | ./build.sh integrate |
src/tooling/docs-builder/ | ./build.sh unit-test |
| Multiple areas or uncertain | ./build.sh unit-test |
If files span more than two source areas, prefer ./build.sh unit-test to run all unit tests at once.
./build.sh integrate) require cloned repos and take significantly longer — only run when integration test files changed or the user explicitly asks./build.sh unit-test is the safe default (completes in under a minute)npm run compile:check from src/Elastic.Documentation.Site/