Pages: Changelog
Guides changelog and release notes pages. Typically at changelog.* subdomain or /changelog. Builds trust, reduces support, increases feature adoption.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product and release cadence.
Identify:
- Product type: SaaS, API, mobile app, etc.
- Audience: End users, developers, both
- Release cadence: Weekly, monthly, continuous
- Format: Timeline, version-based, category (New, Improved, Fixed)
Changelog Structure
| Section |
Purpose |
| Entry |
Date, version, title |
| Category |
New, Improved, Fixed, Deprecated (optional) |
| Description |
What changed, why it matters |
| Link |
To docs, blog, or in-app |
| Media |
Screenshots, GIFs, videos (optional) |
Best Practices
Content
- User benefit first: "You can now X" not "We added X"
- Concrete: Specific features, not vague "improvements"
- Scannable: Headlines, bullets, tags
- Searchable: If many entries, add search/filter
Organization
- Reverse chronological: Newest first
- Grouping: By version or date range
- Tags: Feature area, product module (optional)
- RSS/email: Notify subscribers of updates
Placement
- Subdomain: changelog.yourdomain.com
- Path: /changelog, /updates, /releases
- Embed: Widget in app or docs sidebar
- Link from: Footer, docs, in-app
Output Format
- Structure (layout, entry format)
- Entry template (fields, tone)
- Navigation (filters, search)
- SEO (index, metadata)
- Integration (embed, RSS, email)
Related Skills
- docs-page-generator: Changelog linked from docs
- docs-page-generator: API changelog for developers; docs includes API Reference
- blog-page-generator: Major releases may have blog posts
- top-banner-generator: Announce major updates on main site
1---2name: changelog-page-generator3description: When the user wants to create, optimize, or structure a changelog or release notes page. Also use when the user mentions "changelog", "release notes", "what's new" or "updates". For sitewide page planning, use website-structure.4metadata:5 source: https://skillmd.com/skills/ariadoss/changelog-page-generator6 version: 1.0.17---89# Pages: Changelog1011Guides changelog and release notes pages. Typically at `changelog.*` subdomain or `/changelog`. Builds trust, reduces support, increases feature adoption.1213**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.1415## Initial Assessment1617**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product and release cadence.1819Identify:201. **Product type**: SaaS, API, mobile app, etc.212. **Audience**: End users, developers, both223. **Release cadence**: Weekly, monthly, continuous234. **Format**: Timeline, version-based, category (New, Improved, Fixed)2425## Changelog Structure2627| Section | Purpose |28|---------|---------|29| **Entry** | Date, version, title |30| **Category** | New, Improved, Fixed, Deprecated (optional) |31| **Description** | What changed, why it matters |32| **Link** | To docs, blog, or in-app |33| **Media** | Screenshots, GIFs, videos (optional) |3435## Best Practices3637### Content3839- **User benefit first**: "You can now X" not "We added X"40- **Concrete**: Specific features, not vague "improvements"41- **Scannable**: Headlines, bullets, tags42- **Searchable**: If many entries, add search/filter4344### Organization4546- **Reverse chronological**: Newest first47- **Grouping**: By version or date range48- **Tags**: Feature area, product module (optional)49- **RSS/email**: Notify subscribers of updates5051### Placement5253- **Subdomain**: changelog.yourdomain.com54- **Path**: /changelog, /updates, /releases55- **Embed**: Widget in app or docs sidebar56- **Link from**: Footer, docs, in-app5758## Output Format5960- **Structure** (layout, entry format)61- **Entry template** (fields, tone)62- **Navigation** (filters, search)63- **SEO** (index, metadata)64- **Integration** (embed, RSS, email)6566## Related Skills6768- **docs-page-generator**: Changelog linked from docs69- **docs-page-generator**: API changelog for developers; docs includes API Reference70- **blog-page-generator**: Major releases may have blog posts71- **top-banner-generator**: Announce major updates on main site