| name | docs-serverless-changelog |
| version | 1.0.1 |
| description | Convert raw Markdown tool output into Elastic Cloud Serverless changelog format using GitHub PR context and prior Serverless release notes. Use when drafting or editing Serverless changelog entries from release notes generator output. |
| argument-hint | <path-to-raw-rn.md> |
| disable-model-invocation | true |
| context | fork |
| allowed-tools | Read, Grep, Bash(gh *) |
| sources | ["https://github.com/elastic/docs-content/tree/main/release-notes/elastic-cloud-serverless"] |
You are an assistant to the documentation team. Convert raw Markdown tool output into the Serverless Changelog Markdown format, using GitHub context to improve accuracy and user value. Use prior Serverless release notes from the docs-content repo to match established voice, tone, and formatting.
When to use this skill
- The user has raw
.md output from a release notes generator that needs to be converted to Serverless changelog format.
- The user wants you to look at every PR listed in the release notes (and any PRs referenced) to verify accuracy and improve user-facing wording.
- Input: path to the raw
.md file (or paste content).
0) Response format (required)
Your response must contain two parts, in this exact order:
- Release notes Markdown inside a single fenced code block (for copy/paste).
- Notes (Confidence + Assumptions) outside the code block, where you explicitly call out:
- The release-note bullets you have the least confidence in (and why).
- Any bolding uncertainty (button/page title vs feature name).
- Any assumptions you made (repo choice, section mapping, terminology normalization, etc.).
- Any input anomalies (missing PR numbers, unclear ownership, ambiguous scope).
- What prior release notes you referenced (directory + files), or why they couldn't be fetched.
1) Output: required structure (default and preferred)
-
Top header: Use a level-2 header with date and anchor:
## Month Day, Year [serverless-changelog-MMDDYYYY]
- Date format:
Month Day, Year (for example, March 23, 2026)
- Anchor format:
serverless-changelog- + MMDDYYYY (zero-padded), for example serverless-changelog-03232026
-
Headings: There must be only two section headings (in this order):
### Features and enhancements [serverless-changelog-MMDDYYYY-features-enhancements]### Fixes [serverless-changelog-MMDDYYYY-fixes]
-
Ignore tool sub-headings: Discard any component/category headers from the tool output (for example, "Discover", "Management", "Elastic Observability solution", "Dashboards and Visualizations"). All bullets must flow under the two section headings above.
