菜单
Convert raw Kibana release notes tool output into Stack release notes (Elastic Observability or Elastic Security) using GitHub PR context and prior release notes. Use when drafting or editing Stack 9.x release notes from the Kibana release notes generator output.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/elastic/elastic-docs-skills --skill docs-kibana-release-notes命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Suggest improved text for changelog YAML files against current Elastic standards. Mirrors the pattern catalog from docs-review-changelog to provide consistent fixes. Includes type-title alignment, product/surface context for titles, description verb-tense (third-person present), and technical content assessment. Features repository-aware area validation and enhanced confidence scoring. Supports single files or directories. Fetches canonical guidance to stay in sync. Use after review identifies quality issues, or when drafting new changelogs.
Validate and assess the quality of Elastic changelog YAML files against current Elastic standards. Reports schema errors, content quality issues, systematic pattern violations, type-title alignment mismatches, missing product/surface context in titles, description verb-tense issues, and overly technical content that needs user-focused rewrites. Features repository-aware area validation. Fetches canonical guidance to stay in sync. Use when checking or reviewing changelog files before merging — pairs with docs-fix-changelog to get suggested fixes.
Validate and generate applies_to tags in Elastic documentation, including for cumulative docs across versions and deployment types. Use when writing new docs pages, reviewing existing pages for correct applies_to usage, deciding whether to preserve or replace existing version-scoped content, or when content changes lifecycle state (experimental, preview, beta, GA, deprecated, removed).
正在显示 SKILL.md
基于 SOC 职业分类
| name | docs-kibana-release-notes |
| version | 1.0.1 |
| description | Convert raw Kibana release notes tool output into Stack release notes (Elastic Observability or Elastic Security) using GitHub PR context and prior release notes. Use when drafting or editing Stack 9.x release notes from the Kibana release notes generator output. |
| argument-hint | <path-to-raw-rn.md> [observability|security] [version] |
| disable-model-invocation | true |
| context | fork |
| allowed-tools | Read, Grep, Bash(gh *) |
| sources | ["https://release-notes.kibanateam.dev/","https://github.com/elastic/docs-content/tree/main/release-notes/elastic-observability","https://github.com/elastic/docs-content/tree/main/release-notes/elastic-security"] |
You are an assistant to the documentation team. Convert raw .md tool output from the Kibana release notes generator into the Stack release notes Markdown format for Elastic Observability or Elastic Security, using GitHub PR context to improve accuracy and user value. Use prior Stack release notes from the docs-content repo to match established voice, tone, and formatting.
.md output from the Kibana release notes generator and (optionally) added Observability or Security release notes..md file (or paste content), and optionally solution (observability or security) and Stack version (e.g. 9.3.2).Your response must contain two parts, in this exact order:
Top header: Use a level-2 header with the Stack version number:
## VERSION [elastic-SOLUTION-VERSION-release-notes]
elastic- + solution name + - + version + -release-notes, e.g. elastic-observability-9.3.2-release-notes or elastic-security-9.3.2-release-notes.Headings: For now, there must be (in this order):
### Features and enhancements [elastic-SOLUTION-VERSION-features-enhancements]### Fixes [elastic-SOLUTION-VERSION-fixes]Ignore tool sub-headings: Discard any component/category headers from the tool output (e.g. "Discover", "Management", "Elastic Observability solution", "Dashboards and Visualizations"). All bullets must flow under the two section headings above.
.md tool output): the source list of release-note candidates and any provided phrasing/categorization..md intent.https://github.com/elastic/docs-content/tree/main/release-notes/elastic-observabilityhttps://github.com/elastic/docs-content/tree/main/release-notes/elastic-securityBefore writing final output:
index.md file in the appropriate directory within elastic/docs-content:
release-notes/elastic-observability/index.md for Elastic Observability release notesrelease-notes/elastic-security/index.md for Elastic Security release notesIf the directory cannot be fetched (not found / permission / tooling limitation):
For each PR number found in the tool output:
.md tool outputMap tool sections to the two output sections:
Features (release_note:feature) → Features and enhancementsEnhancements (release_note:enhancements) → Features and enhancementsFixes (release_note:fix) → FixesUnexpected sections (e.g. breaking changes, known issues, deprecations, security notices):
Extract PR numbers:
#123456(opens in a new tab or window) to 123456..md text is sufficiently clear on its own).Every bullet that references a PR must end with:
[#123456]({{kib-pull}}123456) for Kibana PRsNo bare URLs. Always use the Handlebars-style variables above.
If repo is uncertain:
Component names / UI elements:
Technical terms: Use backticks for code-level syntax, operators, commands, settings, and parameters (e.g. STATS, concat, on_disk_rescore, approximate).
ES|QL normalization: Use {{esql}} (not "ES|QL" or variants). Put specific commands/functions in backticks.
Product variables: Use {{esql}}, {{kib}}, {{serverless-full}} where appropriate. Keep variables exactly formatted with double curly braces.
Software context: The software is from Elastic (may relate to Elasticsearch, Elastic Observability, or Elastic Security). Use this context for correct terminology; do not add marketing language.
## header and exactly two ### headers (in the required order).elastic-SOLUTION-VERSION-release-notes (e.g. elastic-observability-9.3.2-release-notes).[#]({{...}}) link when repo is known.{{esql}} used consistently.release-notes were referenced (or why they couldn't be fetched).