Changelog Page Generator
Structure a trustworthy changelog or release-notes page that cuts support load and helps users discover new features.
Overview
Changelog Page Generator is an agent skill most often used in Launch (also Ship launch prep and Grow lifecycle) that structures changelog and release-notes pages to build trust and drive feature adoption.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill changelog-page-generatorWhat is this skill?
- Guides changelog placement at changelog.* subdomain or /changelog with audience and cadence assessment
- Defines entry structure: date, version, title, categories (New, Improved, Fixed, Deprecated), descriptions, and doc link
- Supports SaaS, API, and mobile products with timeline, version-based, or category-based formats
- Reads .claude/project-context.md or .cursor/project-context.md when present for release cadence
- Explicit handoff to website-structure skill for full sitewide page planning
- Metadata version 1.0.1
Adoption & trust: 734 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You ship often but users miss updates, support repeats the same questions, and you have no clear changelog format or URL.
Who is it for?
SaaS, API, or app solos with weekly-to-continuous releases who need a public what-is-new page without hiring product marketing.
Skip if: One-off internal-only release notes with no public page, or full marketing site architecture—use website-structure for sitewide planning instead.
When should I use this skill?
User wants to create, optimize, or structure a changelog or release notes page, or mentions changelog, release notes, what's new, updates, product updates, version history, or changelog.yourdomain.com.
What do I get? / Deliverables
You get an assessed changelog information architecture with categorized entries, linking patterns, and format choices matched to your release cadence.
- Changelog information architecture
- Entry and category templates
- Audience-specific format recommendation
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Primary shelf is Launch because public changelog URLs are a core distribution and trust surface when you ship updates. Distribution fits ongoing release communication at changelog subdomain or /changelog paths aimed at end users and developers.
Where it fits
Draft categorized release notes before a versioned deploy goes live.
Stand up changelog.yourdomain.com with timeline entries linked from the footer and docs.
Turn changelog entries into onboarding nudges and email digests for dormant users.
Mirror in-app feature docs to changelog descriptions so dev and user audiences stay aligned.
How it compares
Use for a dedicated changelog IA and copy framework, not as a substitute for automated CI release-note generators alone.
Common Questions / FAQ
Who is changelog-page-generator for?
Indie founders and small teams publishing SaaS, APIs, or mobile apps who need a credible public changelog that end users and developers can scan.
When should I use changelog-page-generator?
Before Launch when planning changelog.yourdomain.com; after Ship when drafting release notes; during Grow when improving lifecycle emails and in-app what-is-new links.
Is changelog-page-generator safe to install?
It is editorial guidance only—review the Security Audits panel on this Prism page before trusting any bundled automation from the same repo.
SKILL.md
READMESKILL.md - Changelog Page Generator
# 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: 1. **Product type**: SaaS, API, mobile app, etc. 2. **Audience**: End users, developers, both 3. **Release cadence**: Weekly, monthly, continuous 4. **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