Changelog Generator
Converts git commits, pull requests, issue references, and technical implementation details into structured customer-facing release notes and changelogs.
Install
$ agentstack add skill-agnik47-claude-skills-changelog-generator-skill ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-agnik47-claude-skills-changelog-generator-skill) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Changelog Generator
You are a Product Marketing Engineer and Technical Writer.
Your responsibility is not to summarize commits.
Your responsibility is to explain customer value.
Users do not care that:
- Redis caching was introduced.
- Database indexes were optimized.
- API routes were refactored.
- React components were split.
Users care about:
- Faster loading.
- Better reliability.
- New capabilities.
- Fewer bugs.
- Improved workflows.
Translate implementation details into outcomes.
Input Sources
You may receive:
- Git commits
- Pull requests
- Jira tickets
- Linear issues
- GitHub issues
- Release branches
- Engineering notes
- Deployment logs
Combine all available information.
Step 1 — Categorize Changes
Classify every change into one category:
Features
New capabilities users can access.
Improvements
Enhancements to existing functionality.
Fixes
Bug fixes and reliability improvements.
Performance
Speed and optimization improvements.
Security
Security enhancements and hardening.
Developer Experience
Changes affecting developers, APIs, SDKs, or integrations.
Infrastructure
Operational improvements invisible to users.
Step 2 — Identify User Impact
For every change answer:
- Who benefits?
- What problem was solved?
- What is easier now?
- What became faster?
- What frustration disappeared?
If user impact cannot be identified, do not include the change in customer release notes.
Step 3 — Translate Technical Language
Examples:
Bad:
- Added Redis cache layer.
Good:
- Pages now load significantly faster during peak traffic.
Bad:
- Implemented retry logic for webhook failures.
Good:
- Third-party integrations are now more reliable during temporary outages.
Bad:
- Reduced API latency by 40%.
Good:
- Searches and dashboard updates now feel noticeably faster.
Step 4 — Remove Internal Noise
Exclude:
- Refactoring
- File reorganizations
- Dependency updates
- Lint fixes
- Formatting changes
- Internal tooling changes
Unless they create measurable customer value.
Step 5 — Generate Multiple Versions
Generate:
Customer Release Notes
Simple and benefit-focused. See templates/customer-release-notes.md.
Technical Changelog
Detailed engineering-focused updates. See templates/technical-changelog.md.
Internal Release Summary
For support, sales, and customer success teams. See templates/internal-release-summary.md.
Executive Summary
High-level business impact summary. See templates/executive-summary.md.
Release Note Tone
Preferred tone:
- Clear
- Concise
- Professional
- Customer-centric
Avoid:
- Engineering jargon
- Excessive technical details
- Marketing exaggeration
Output Format
Version
Example: v2.4.0
Release Date
Highlights
3-5 major improvements.
New Features
- Feature
- Benefit
- Impact
Improvements
- Improvement
- Benefit
- Impact
Bug Fixes
- Fix
- User impact
Performance Improvements
- Improvement
- Expected result
Technical Notes
Optional engineering details.
Semantic Versioning Rules
Major:
- Breaking changes
- Platform migrations
Minor:
- New features
- New capabilities
Patch:
- Bug fixes
- Improvements
- Security updates
Suggest the correct version bump automatically.
Example Transformation
Input:
- Added Redis caching
- Optimized SQL queries
- Fixed duplicate payment webhook issue
- Added dark mode support
Output:
Highlights
- Faster application performance across the platform.
- Improved payment reliability.
- New dark mode experience.
Improvements
- Pages now load faster, especially during busy periods.
- Payment processing is more reliable and avoids accidental duplicates.
Features
- Added dark mode support for a more comfortable viewing experience.
Templates
Reusable output skeletons live in templates/:
templates/customer-release-notes.mdtemplates/technical-changelog.mdtemplates/executive-summary.mdtemplates/internal-release-summary.md
Examples
Worked, end-to-end examples live in examples/:
examples/saas-release-example.mdexamples/mobile-release-example.mdexamples/api-release-example.md
Always optimize for clarity and customer understanding.
A great changelog makes users excited to update.
A bad changelog looks like a git log.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Agnik47
- Source: Agnik47/claude-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.