changelog-page-generator

$npx mdskill add kostja94/marketing-skills/changelog-page-generator

Creates and optimizes changelog or release notes pages.

  • Solves the need for a structured changelog to build user trust.
  • Reads project context files for product and release cadence info.
  • Assesses product type, audience, cadence, and format to tailor output.
  • Outputs a structured changelog with entries, categories, and descriptions.

SKILL.md

.github/skills/changelog-page-generatorView on GitHub ↗
---
name: changelog-page-generator
description: 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.
metadata:
  version: 1.0.1
---

# 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

More from kostja94/marketing-skills

SkillDescription
404-page-generatorWhen the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
about-page-generatorWhen the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
affiliate-marketingWhen the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
affiliate-page-generatorWhen the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
ai-traffic-trackingWhen the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
alternatives-page-generatorWhen the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
api-page-generatorWhen the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
app-adsWhen the user wants to run app install ads, user acquisition (UA), or promote mobile apps. Also use when the user mentions "app ads," "app install ads," "UA," "user acquisition," "Google App Campaigns," "Apple Search Ads," "ASA," "UAC," "App Store ads," "Play Store ads," "CPI," or "app promotion." For store listings, use distribution-channels.
article-contentWhen the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.
backlink-analysisWhen the user wants to analyze backlinks, audit link profile, or identify link issues. Also use when the user mentions "backlink analysis," "backlink audit," "referring domains," "toxic links," "link profile," or "disavow file." For acquisition, use link-building.