| name | release-blog-writer |
| description | Write or revise release blog posts for product releases. Use when the user asks to draft, polish, restructure, or adapt a release announcement. |
| metadata | {"internal":true} |
Release blog writer
Purpose
Use this skill to write release blogs that feel like product communication, not raw changelog output. The blog may be written in English, Chinese, or another user-requested language, but these instructions stay language-agnostic and project-agnostic.
Core writing rules
- Follow the user's requested language and the style of existing release blogs for the same product.
- Use previous major or minor release posts as the primary style reference when available.
- Prefer clear user value over implementation trivia.
- Avoid turning the blog into a complete changelog.
Recommended shape
Use the project's existing blog metadata and component conventions. If the product has neighboring release posts, mirror their frontmatter, author block, date format, title style, and navigation pattern.
Section writing
Each feature section should usually follow this pattern:
- Describe the change clearly so readers understand its background, purpose, use cases, and user-facing benefits such as performance gains.
- Avoid exhaustive API lists; select the key APIs or behaviors readers need, and when useful, use one precise code or configuration example to make the change clear at a glance.
Headings
- Use sentence case for titles and headings.
- Keep headings short and specific.
- Keep anchors stable and readable.
- If the website is built with Rspress, use the Rspress anchor syntax, such as .
