# Changelog Generator

> Converts git commits, pull requests, issue references, and technical implementation details into structured customer-facing release notes and changelogs.

- **Type:** Skill
- **Install:** `agentstack add skill-agnik47-claude-skills-changelog-generator-skill`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [Agnik47](https://agentstack.voostack.com/s/agnik47)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [Agnik47](https://github.com/Agnik47)
- **Source:** https://github.com/Agnik47/claude-skills/tree/main/changelog-generator.skill

## Install

```sh
agentstack add skill-agnik47-claude-skills-changelog-generator-skill
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## 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.md`
- `templates/technical-changelog.md`
- `templates/executive-summary.md`
- `templates/internal-release-summary.md`

# Examples

Worked, end-to-end examples live in `examples/`:

- `examples/saas-release-example.md`
- `examples/mobile-release-example.md`
- `examples/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](https://github.com/Agnik47)
- **Source:** [Agnik47/claude-skills](https://github.com/Agnik47/claude-skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-agnik47-claude-skills-changelog-generator-skill
- Seller: https://agentstack.voostack.com/s/agnik47
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.
