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-generator
3description: 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," "updates," "product updates," "version history," or "changelog.yourdomain.com." For sitewide page planning, use website-structure.
4metadata:
5 version: 1.0.1
6---
7
8# Pages: Changelog
9
10Guides changelog and release notes pages. Typically at `changelog.*` subdomain or `/changelog`. Builds trust, reduces support, increases feature adoption.
11
12**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.
13
14## Initial Assessment
15
16**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product and release cadence.
17
18Identify:
191. **Product type**: SaaS, API, mobile app, etc.
202. **Audience**: End users, developers, both
213. **Release cadence**: Weekly, monthly, continuous
224. **Format**: Timeline, version-based, category (New, Improved, Fixed)
23
24## Changelog Structure
25
26| Section | Purpose |
27|---------|---------|
28| **Entry** | Date, version, title |
29| **Category** | New, Improved, Fixed, Deprecated (optional) |
30| **Description** | What changed, why it matters |
31| **Link** | To docs, blog, or in-app |
32| **Media** | Screenshots, GIFs, videos (optional) |
33
34## Best Practices
35
36### Content
37
38- **User benefit first**: "You can now X" not "We added X"
39- **Concrete**: Specific features, not vague "improvements"
40- **Scannable**: Headlines, bullets, tags
41- **Searchable**: If many entries, add search/filter
42
43### Organization
44
45- **Reverse chronological**: Newest first
46- **Grouping**: By version or date range
47- **Tags**: Feature area, product module (optional)
48- **RSS/email**: Notify subscribers of updates
49
50### Placement
51
52- **Subdomain**: changelog.yourdomain.com
53- **Path**: /changelog, /updates, /releases
54- **Embed**: Widget in app or docs sidebar
55- **Link from**: Footer, docs, in-app
56
57## Output Format
58
59- **Structure** (layout, entry format)
60- **Entry template** (fields, tone)
61- **Navigation** (filters, search)
62- **SEO** (index, metadata)
63- **Integration** (embed, RSS, email)
64
65## Related Skills
66
67- **docs-page-generator**: Changelog linked from docs
68- **docs-page-generator**: API changelog for developers; docs includes API Reference
69- **blog-page-generator**: Major releases may have blog posts
70- **top-banner-generator**: Announce major updates on main site
kostja94