kostja94/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 https://github.com/kostja94/marketing-skills --skill changelog-page-generatorGuides 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.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product and release cadence.
Identify:
| 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) |
Take kostja94/changelog-page-generator from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.