changelog-generator

Name: changelog-generator
Author: Composio

Generate clear user-facing changelogs and release notes from Git commit history.

Stars

★ 77,656

Source

GitHub

Updated

2026-10-22

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This appears to be an open-source, prompt-only changelog generation skill. The materials do not show any need for secrets, remote connections, or self-contained local code execution; its main function is to analyze local git commits and possibly read repository guidance files, so overall risk is low.

CredentialsLow risk

The materials explicitly state that no keys or environment variables are required, and the README does not ask for external logins or tokens; no obvious credential exposure or abuse surface is shown.

Network egressLow risk

No remote endpoints are declared, and the README only describes generating changelogs from local git history; there is no evidence of sending user data, commit contents, or repository information to external services.

Code executionLow risk

The system flags it as prompt-only, and the materials do not show executable installation steps, script execution, background processes, or additional system capability use.

Data accessCaution

By design, the skill analyzes git commit history and may reference repository files such as CHANGELOG_STYLE.md; this means it typically needs access to the current project repository, but the materials do not show excessive read/write behavior or cross-directory access beyond that scope.

Supply chainLow risk

The source is an open GitHub repository with very strong community adoption (64.7k stars), which is a strong positive signal; while the license is unspecified and maintenance status is unknown, there are no concrete supply-chain red flags such as closed-source data exfiltration or suspicious dependencies.

Recommendations

Use it only within the intended project repository and avoid running it on repositories with sensitive commit history unless necessary.
Review the generated changelog before publishing to prevent accidental disclosure of internal implementation details or sensitive security-fix context.
If it reads style files or commit history, ensure the repository does not contain secrets, private ticket links, or internal code names that should not be surfaced.
Prefer pinning and reviewing the exact open-source version in use, and monitor future maintenance and licensing details.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "changelog-generator" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/changelog-generator/SKILL.md
2. Save it as ~/.claude/skills/changelog-generator/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Changelog Generator

This skill transforms technical git commits into polished, user-friendly changelogs that your customers and users will actually understand and appreciate.

When to Use This Skill

Preparing release notes for a new version
Creating weekly or monthly product update summaries
Documenting changes for customers
Writing changelog entries for app store submissions
Generating update notifications
Creating internal release documentation
Maintaining a public changelog/product updates page

What This Skill Does

Scans Git History: Analyzes commits from a specific time period or between versions
Categorizes Changes: Groups commits into logical categories (features, improvements, bug fixes, breaking changes, security)
Translates Technical → User-Friendly: Converts developer commits into customer language
Formats Professionally: Creates clean, structured changelog entries
Filters Noise: Excludes internal commits (refactoring, tests, etc.)
Follows Best Practices: Applies changelog guidelines and your brand voice

How to Use

Basic Usage

From your project repository:

Create a changelog from commits since last release

Generate changelog for all commits from the past week

Create release notes for version 2.5.0

With Specific Date Range

Create a changelog for all commits between March 1 and March 15

With Custom Guidelines

Create a changelog for commits since v2.4.0, using my changelog 
guidelines from CHANGELOG_STYLE.md

Example

User: "Create a changelog for commits from the past 7 days"

Output:

# Updates - Week of March 10, 2024

## ✨ New Features

- **Team Workspaces**: Create separate workspaces for different 
  projects. Invite team members and keep everything organized.

- **Keyboard Shortcuts**: Press ? to see all available shortcuts. 
  Navigate faster without touching your mouse.

## 🔧 Improvements

- **Faster Sync**: Files now sync 2x faster across devices
- **Better Search**: Search now includes file contents, not just titles

## 🐛 Fixes

- Fixed issue where large images wouldn't upload
- Resolved timezone confusion in scheduled posts
- Corrected notification badge count

Inspired by: Manik Aggarwal's use case from Lenny's Newsletter