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.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
A feature flag is additive. Flag off keeps the previous default. Flag on adds new behavior only.
Read this skill before you add any of these:
FeatureFlagsfeature_flags YAML keyFEATURE_* environment overrideif (flag) around a code pathsrc/Elastic.Documentation.Configuration/Builder/FeatureFlags.csFEATURE_<UPPER_SNAKE>feature_flags in config/assembler.yml as UPPER_SNAKEprod when you create itPublishEnvironment.ToFeatureFlags() in src/Elastic.Documentation.Configuration/Assembler/PublishEnvironment.cs loads YAML keys through Set()tests/Elastic.Documentation.Build.Tests/FeatureFlagsTests.csFlag off equals the previous default in behavior. Flag on adds new behavior only.
Do not move, hide, relocate, or delete existing output when you introduce the flag.
New behavior is a new panel, a new build step, or a new field. It is not a relocated copy of something that already shipped.
FeatureFlags. The default stays false.prod as part of creating it.Put the if (flag) around new code. Leave the existing branch as it was.
Shared markup, layout, and data wiring that the old path still needs stay outside the flag.
This step is required. Do not skip it.
Do not ship a flag whose existing behavior lives only on the new path.
Do not treat "the new path has it" as coverage for the old path.
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.
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.
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.