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.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
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; shared views or layout CSS also npm run visual:seed once, then npm run visual:check |
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/No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
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.
The English summary is being prepared. Showing the original description.
Registers a feature flag as additive-only and verifies the flag-off path still matches the previous default. Use whenever adding or extending a feature flag, editing FeatureFlags.cs, changing feature_flags in assembler.yml, gating a code path behind a FEATURE_* environment variable, or enabling a flag in an environment. Do not skip this skill for flag work even if the user does not name it.
The English summary is being prepared. Showing the original description.
File a well-formed bug report or feature request. Use when the user asks to open an issue, report a bug, or request a feature in the docs-builder repo.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.