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.
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.
The English summary is being prepared. Showing the original 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.
The English summary is being prepared. Showing the original description.
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.
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.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)