Skip to main content
affpapa.org
RU EN
skill CX Codex

changelog-generator · composio-community — Claude Code skill: release notes from git

Turns git history into a user-facing changelog: sorts commits into categories and rewrites developer messages for customers.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add composio-community/awesome-claude-plugins --skill changelog-generator -a claude-code
Open on GitHub

What changelog-generator does

The skill walks the commit history for a date range or between two versions. Commits land in buckets — new features, improvements, bug fixes, breaking changes, security — and internal work like refactoring or tests gets dropped from the public notes.

What a developer wrote in a commit message becomes wording a customer can read. Formatting follows your guidelines if a CHANGELOG_STYLE.md sits in the repo; otherwise the skill sticks to standard changelog practice. Run it from the repository root so it sees the full history.

Read the draft before you publish it. The skill produces the first pass; you own the meaning, and the breaking-changes section is where a wrong line costs the most.

What it helps with

  • write release notes for a new version
  • put together a weekly product update summary
  • rewrite commit messages for end users
  • keep refactoring and test commits out of the public changelog
  • draft an app store update description

Example prompts for the agent

  • Create a changelog from commits since the last release
  • Generate a changelog for all commits from the past week
  • Write release notes for version 2.5.0 using my guidelines from CHANGELOG_STYLE.md

How to install changelog-generator

1Skills CLI (Vercel)

npx skills add composio-community/awesome-claude-plugins --skill changelog-generator -a claude-code

2Manually: put the files in place

~/.claude/skills/changelog-generator/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/changelog-generator/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about changelog-generator

How do I install changelog-generator in Claude Code?

Run npx skills add composio-community/awesome-claude-plugins --skill changelog-generator -a claude-code. The skill file then lives at ~/.claude/skills/changelog-generator/SKILL.md.

What does changelog-generator do?

It reads the git history, groups commits into categories and rewrites them as release notes that users can follow.

How does the skill decide on changelog style?

Standard changelog guidelines apply unless you point it at a CHANGELOG_STYLE.md in the repository and name that file in your request.

Similar skills

Everything for Writing and docs →

changelog-generator by other authors comes first.

changelog-generator Alireza Rezvani Builds release notes from Conventional Commits, suggests a SemVer bump, and lints commit messages. Use it for releases, CI, and hotfix work. 618installs grill-with-docs Matt Pocock This skill interviews you about a plan or design and creates ADRs and a glossary along the way. Use it when decisions need sharper definition. 1,219,756installs skill-creator official anthropics Creates and refines skills, then tests them with prompts, evaluations, and performance checks. 414,180installs setup-matt-pocock-skills Matt Pocock This skill configures a repository for Matt Pocock's engineering skills by setting its issue tracker, triage labels, and domain docs layout. Run it before using the other skills. 1,052,851installs handoff Matt Pocock Creates a handoff document from the current conversation so another agent can continue the work. Use it when a task moves to a new session or agent. 1,038,491installs triage Matt Pocock This skill moves issues and external PRs through triage states, verification, and agent briefs. It fits maintainers managing an issue queue. 990,453installs domain-modeling Matt Pocock This skill sharpens project terminology, maintains GLOSSARY.md, and records selected architecture decisions in ADRs. Use it while the domain model is changing. 876,391installs

From the same set8

perf-investigation-logger Appends structured performance investigation notes, quotes, and evidence to project logs. Keeps benchmarks and optimization decisions organized. CX Codex +1 1,600installs perf-theory-tester A skill that keeps perf experiments honest: one change per hypothesis, repeated runs, a recorded verdict. Useful when you need proof that an optimization helped. CX Codex +1 1,500installs perf-profiler Runs profilers against CPU and memory hot paths, captures flame graphs, and records file and line evidence. CX Codex +1 1,600installs perf-code-paths This skill maps likely execution paths, entrypoints, and related files for a performance scenario before profiling. Useful when the hot area is unclear. CX Codex +1 1,600installs perf-theory-gatherer A skill that turns git history and code evidence into up to five hypotheses about a performance problem. CX Codex +1 1,600installs perf-benchmarker Runs benchmarks sequentially under strict duration rules to catch performance regressions and set baseline metrics. CX Codex +1 1,600installs perf-analyzer Turns profiling and experiment results into evidence-backed performance recommendations. Use it when a decision needs a traceable basis. CX Codex +1 1,600installs

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor