changelog-from-commits
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.
npx skills add mohitagw15856/pm-claude-skills --skill changelog-from-commits --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Changelog from Commits (Live) Users don't read commit messages, and they shouldn't have to. In Claude Cowork this skill reads the *real* commit range and turns it into a changelog written for the people who use the software — grouped, deduped, and translated from "refactor: extract helper" into what actually changed for them. ## What This Skill Produces - **The changelog** — grouped into Added / Changed / Fixed / Breaking, each entry written as user-facing benefit, not commit-speak - **The breaking-change callout** — migrations and removals pulled to the top with what to do - **A changelog artifact** — Keep-a-Changelog style, ready to paste into `CHANGELOG.md` or a release ## Required Inputs Ask for these if not provided: - **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 ## Framework: Commits → Changelog 1. **Group by impact** — Added / Changed / Fixed / Breaking; drop internal-only churn (chore/ci/refactor) unless it changes behaviour. 2. **Translate** — every entry says what the *user* can no
- What This Skill Produces
- Required Inputs
- Framework: Commits → Changelog
- Execution (Cowork)
- Output Format
- Quality Checks
- Anti-Patterns
- Example Trigger Phrases
What does the changelog-from-commits skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill changelog-from-commits --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.