What do I need to use Changelog from Commits (Live)?

The range; The audience; Version & date.

Is Changelog from Commits (Live) free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Changelog from Commits (Live)

Q: How do I know the Changelog from Commits (Live) output is good?

The skill verifies itself against its own quality checks: Every entry maps to a real commit/PR in the range; Entries read as user benefit, not commit messages; Breaking changes lead and include the migration step; Internal-only churn was excluded (unless it changed behaviour).

🔵 Stable🕐 updated 2026-07-20 🔷 SkillSpec L3 ⚙ ships an executable helper pm-cowork-live

Write a human changelog from the REAL commit history — read the actual commit range via the GitHub connector, not a template. Use when asked to write the changelog for this release, what changed since the last tag, draft release notes from my commits, or summarise this range for users in Cowork. Reads commits/PRs between two refs via the GitHub connector, groups them into user-facing changes (features / fixes / breaking), translates commit-speak into human benefit, and produces a changelog artifact ready for the release.

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

🗣 Say this to your agent

“Write the changelog since the last tag in Cowork.”“Draft release notes from my commits for v2.0.”“What changed for users between v1.4 and HEAD?”“Summarise this commit range as a human changelog.”

What to give it

▸The range — from tag/ref to tag/ref (default: last tag → HEAD), and the repo

▸The audience — end users, API consumers, or developers — translation depth follows

▸Version & date — the release number and date for the heading

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓Every entry maps to a real commit/PR in the range

✓Entries read as user benefit, not commit messages

✓Breaking changes lead and include the migration step

✓Internal-only churn was excluded (unless it changed behaviour)

✓Multiple commits behind one feature are a single line

⚠️ What it refuses to do

**Pasting raw commit messages** as the changelog.

**Inventing a feature** not in the range to round it out.

**Burying a breaking change** in the middle of "Changed".

**Listing every `chore:`/`refactor:`** that users never see.

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="changelog-from-commits"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Changelog from Commits (Live) is one of 750 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog