Changelog Generator

VerifiedSafe

Analyzes commits and changed files to produce structured release notes in Markdown.

Sby Skills Guide Bot
DocumentationBeginner
7/26/2026
Claude CodeCursorCodex
#changelog#release-notes#git#markdown#commit-analysis

Recommended for

Automated summary

Analyzes git history and changed files to produce a structured Markdown changelog or release notes, grouped into features, fixes, performance, chores, and documentation.

Strengths

  • Buckets changes into five explicit categories (Features, Bug Fixes, Performance, Chores, Documentation)
  • Output is Markdown ready for CHANGELOG.md or GitHub Releases
  • Follows a clear four-step flow: read the git log, assess scope, draft notes, format output
  • Ships a helper script (scripts/get-changes.sh) that also summarizes unstaged changes

Limitations

  • Quality depends heavily on how descriptive the underlying commit messages are
  • Does not handle semantic version numbering, tagging, or actually publishing a release
  • Relies on a local bash script that must be permitted to run in the environment
When to use it

Use it when preparing a release or summarizing recent work in a git repository.

When not to use it

Avoid it on projects with no git history, a squashed history, or meaningless commit messages.

Security analysis

Safe
Quality score78/100

The skill only instructs the agent to inspect git history and format changelog notes. It does not request destructive commands, exfiltration, obfuscated payloads, or safety disables. The referenced helper script is not shown, but there is no indication of malicious behavior.

No concerns found

How this analysis is made

Examples

Release changelog
Look at the commits since the last release tag and write a Markdown changelog entry for version 1.2.0, grouped into features, fixes, performance, chores, and docs.
Summarize recent work
Summarize everything I've changed in the last two weeks as GitHub release notes, grouped by category.
Include unstaged work
Run scripts/get-changes.sh and combine the unstaged changes with the recent git log into a single changelog draft.

name: change-writer description: Generates clean, human-readable changelogs and release notes from git commits and file changes. Use when preparing for a release or summarizing recent work.

Change Writer Skill

This skill analyzes recent changes in the repository to generate structured changelogs. It categorizes changes into Features, Fixes, and Refactors.

Instructions

  1. Analyze History: Run the git log command to see recent changes.
  2. Identify Impact: Look at changed files to understand the scope (e.g., UI, logic, infrastructure).
  3. Draft Notes: Group changes by type (Feat, Fix, Chore, Docs).
  4. Format: Output in Markdown format compatible with CHANGELOG.md or GitHub Releases.

Categories

  • πŸš€ Features: New functionality.
  • πŸ› Bug Fixes: Resolving issues.
  • ⚑ Performance: Speed optimizations.
  • 🧹 Chores: Internal tasks, dependency updates.
  • πŸ“ Documentation: Changes to docs.

Example Output

## [1.2.0] - 2025-12-27

### πŸš€ Features
- Added `Zustand` store for global theme management.
- Implemented `api-expert` skill for better backend integration.

### πŸ› Bug Fixes
- Fixed keyboard avoiding view overlap on Android.
- Resolved race condition in auth flow.

### 🧹 Chores
- Updated `expo` to SDK 54.
- Cleaned up unused assets.

Run scripts/get-changes.sh to see a summary of unstaged changes.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/changelog-generator-ms1aw5jy/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/changelog-generator-ms1aw5jy' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/changelog-generator-ms1aw5jy/download' --output '.skill-downloads/changelog-generator-ms1aw5jy/SKILL.md.part' && mv '.skill-downloads/changelog-generator-ms1aw5jy/SKILL.md.part' '.skill-downloads/changelog-generator-ms1aw5jy/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/changelog-generator-ms1aw5jy/SKILL.md' && test -s '.skill-downloads/changelog-generator-ms1aw5jy/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/change-writer' && cp -R '.skill-downloads/changelog-generator-ms1aw5jy' '.claude/skills/change-writer'

Cursor
test -f '.skill-downloads/changelog-generator-ms1aw5jy/SKILL.md' && test -s '.skill-downloads/changelog-generator-ms1aw5jy/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/change-writer' && cp -R '.skill-downloads/changelog-generator-ms1aw5jy' '.cursor/skills/change-writer'

Codex
test -f '.skill-downloads/changelog-generator-ms1aw5jy/SKILL.md' && test -s '.skill-downloads/changelog-generator-ms1aw5jy/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/change-writer' && cp -R '.skill-downloads/changelog-generator-ms1aw5jy' '.agents/skills/change-writer'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js β‰₯ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/changelog-generator-ms1aw5jy'

openskills read 'changelog-generator-ms1aw5jy'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/changelog-generator-ms1aw5jy/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills