// Create user-focused, SEO-optimized changelog entries for software releases. Use when writing release notes, version updates, product changelogs, or "what's new" documentation for developer tools.
| name | changelog-writer |
| description | Create user-focused, SEO-optimized changelog entries for software releases. Use when writing release notes, version updates, product changelogs, or "what's new" documentation for developer tools. |
| allowed-tools | Read, Grep, Glob, Write, Edit |
Create clear, accurate changelog entries that help developers understand what's new in Lightfast releases.
Before writing anything, verify against docs/architecture/implementation-status/README.md:
Check implementation status to verify:
Never oversell:
Verify every claim:
tldr for AI citation engines, excerpt for listingsSave drafts to: thoughts/changelog/{title-slug}-{YYYYMMDD-HHMMSS}.md
Every draft MUST include:
title, slug, publishedAt (core)excerpt, tldr (AEO)seo.metaDescription, seo.focusKeyword (SEO)_internal.status, _internal.source_prs (traceability)Always use: 0-<version>-lightfast-<feature-slug>
Examples:
0-1-lightfast-github-file-sync-semantic-search0-2-lightfast-pr-metadata-linear-integrationRecommended:
seo.secondaryKeyword, seo.faq[] (enhanced SEO)The frontmatter structure maps directly to ChangelogEntryInput type. Use /publish_changelog to publish drafts to BaseHub.
See resources/templates.md for complete frontmatter template.