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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stage relevant files and create a well-formed git commit. Use this when the user asks to commit changes, save work, or create a commit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a GitHub pull request with a focused why/what body. Use when the user asks to open a PR, create a pull request, or ship a branch.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stage relevant files and create a well-formed git commit. Use this when the user asks to commit changes, save work, or create a commit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a GitHub pull request with a focused why/what body. Use when the user asks to open a PR, create a pull request, or ship a branch.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.