commit
無料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.
日本語の概要は準備中です。原文の説明を表示しています。
elastic/docs-builder252026年10月26日 更新
無料GitHub で公開
test
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.
日本語の概要は準備中です。原文の説明を表示しています。
elastic/docs-builderスター 25(GitHub 25 + cccskills 0)
実行スコア 未検証
インストール方法を見る含まれるファイル（1）
- SKILL.md2.1 KB
SKILL.md（原文）
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Test Skill
Runs the right tests for what changed — fast feedback without running everything.
Steps
1. Detect changed files
git diff --name-only HEAD
Or, if checking staged changes:
git diff --name-only --staged
2. Pick the right test command
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.
3. Run and report
- Show the command being run
- On pass: summarize pass count, confirm all green
- On fail: show the specific failing test(s), the error message, and suggest a fix approach based on the failure
Notes
- Integration tests (
./build.sh integrate) require cloned repos and take significantly longer — only run when integration test files changed or the user explicitly asks - When in doubt,
./build.sh unit-testis the safe default (completes in under a minute) - TypeScript type checking (not tests) is
npm run compile:checkfromsrc/Elastic.Documentation.Site/
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
コメント
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
同じリポジトリのスキル
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.
日本語の概要は準備中です。原文の説明を表示しています。
elastic/docs-builder252026年10月26日 更新
issue
無料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.
日本語の概要は準備中です。原文の説明を表示しています。
elastic/docs-builder252026年10月26日 更新
lint
無料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.
日本語の概要は準備中です。原文の説明を表示しています。
elastic/docs-builder252026年10月26日 更新
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.
日本語の概要は準備中です。原文の説明を表示しています。
elastic/docs-builder252026年10月26日 更新
pr
無料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.
日本語の概要は準備中です。原文の説明を表示しています。
elastic/docs-builder252026年10月26日 更新