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