
Changelog Page Generator
- 761 installs
- 787 repo stars
- Updated June 9, 2026
- kostja94/marketing-skills
changelog-page-generator is a marketing agent skill that automatically generates clear, structured changelog and release notes pages for developers who need trustworthy post-release communication that drives feature adop
About
changelog-page-generator is a kostja94/marketing-skills agent skill for producing structured changelog and release notes pages from release information. The skill guides agents to turn version deltas into readable, trust-building release pages that highlight new features, fixes, and breaking changes in a format users can scan quickly. Developers reach for changelog-page-generator when shipping SaaS or developer tools and need consistent release-note pages instead of ad hoc bullet lists in README files or Discord posts. The skill focuses on clarity, structure, and adoption-oriented framing so shipped features are discoverable after deploy.
- Creates timeline, version-based, or category-driven changelog pages at /changelog or changelog.* subdomains
- Adapts output to product type, audience, and release cadence after reading project-context.md
- Structures each entry with date, version, title, categorized changes (New, Improved, Fixed, Deprecated), impact descript
- Reduces support volume while increasing feature adoption through transparent product history
- First-use guidance explains value before delivering main output; subsequent calls go straight to results
Changelog Page Generator by the numbers
- 761 all-time installs (skills.sh)
- +6 installs in the week ending Jul 25, 2026 (Skillselion tracking)
- Ranked #604 of 1,879 Marketing & SEO skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/kostja94/marketing-skills --skill changelog-page-generatorAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 761 |
|---|---|
| repo stars | ★ 787 |
| Security audit | 3 / 3 scanners passed |
| Last updated | June 9, 2026 |
| Repository | kostja94/marketing-skills ↗ |
How do you generate changelog pages from releases?
Automatically generate clear, structured changelog and release notes pages that build user trust and drive feature adoption.
Who is it for?
Developers and release owners shipping SaaS or developer tools who need repeatable, user-trust-building changelog pages after each version.
Skip if: Teams that only need internal git commit logs, automated semantic-release without narrative copy, or non-software product announcements.
When should I use this skill?
The user mentions changelog page, release notes page, ship communication, or publishing what changed in a new version.
What you get
Structured changelog pages, release notes HTML or markdown, and feature-adoption-oriented ship communications ready to publish.
- Changelog page copy
- Release notes document
Files
SEO: Local
Guides local SEO: Google Business Profile, NAP consistency, and citation building. Businesses with accurate NAP across 40+ authoritative sites see ~19% higher visibility in Google Maps. Use this skill when optimizing for local search, setting up GBP, or auditing citations.
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 Sections 4 (Audience), 5 (Website).
Identify: 1. Business type: Storefront vs service-area 2. Location: Single or multiple 3. Current listings: Existing GBP, directories
NAP Consistency
NAP = Name, Address, Phone. Critical for local rankings.
| Rule | Guideline |
|---|---|
| Exact match | "Street" vs "St." or "LLC" inconsistency = Google may treat as different entities |
| Fix first | Audit and fix inconsistencies before adding new citations |
| Tools | BrightLocal, Whitespark, Moz Local for audit |
Google Business Profile
| Element | Guideline |
|---|---|
| Address | Physical address; no P.O. boxes |
| Description | 750 chars; primary keywords in first 100 |
| Hours | Accurate; seasonal availability |
| Category | Primary category matches business type |
| Service-area | Hide address if no storefront; define service areas |
Citation Building
Targeted precision over submitting to every directory.
Priority order: 1. Google Business Profile 2. Apple Maps 3. Yelp, Bing Places, Facebook 4. Better Business Bureau, Foursquare, Nextdoor 5. Niche directories (Healthgrades, Angi, etc.)
Citation Audit
- Incorrect or outdated data
- Duplicate entries
- Missing listings on key directories
Fix before adding; compounding errors harm rankings.
Output Format
- NAP (exact format for consistency)
- GBP optimization checklist
- Citation priority list
- Audit findings (if applicable)
Related Skills
- geo: GEO for AI search; local + AI overlap
- localization-strategy: Multilingual; local + i18n
- directory-submission: Directory listings; different from local citations
Related skills
FAQ
What does changelog-page-generator produce?
changelog-page-generator produces clear, structured changelog and release notes pages from release information. The skill helps developers communicate version changes in a scannable format that builds user trust and highlights new features.
When should changelog-page-generator run?
changelog-page-generator runs when shipping a new software version and publishing what changed. Use it instead of dumping raw git commits when teams need user-facing release pages that drive feature discovery.
Is Changelog Page Generator safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.