changelog-page-generator
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.
npx skills add kostja94/marketing-skills --skill changelog --agent cursor
Same command for any agent — swap --agent for claude-code, codex, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 a
- Initial Assessment
- Changelog Structure
- Best Practices
- Content
- Organization
- Placement
- Output Format
- Related Skills
What does the changelog-page-generator skill do?
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.
How do I install it?
Run `npx skills add kostja94/marketing-skills --skill changelog --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From kostja94/marketing-skills, a repository with 848 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.